-
Notifications
You must be signed in to change notification settings - Fork 19
Support for static libraries #11
Comments
There really isn't a major reason, one of the biggest is that I really am not proficient in the compiler-linker stuff (or C in general), so I am doing what I can. Someone had mentioned that there are issues with using static libraries too, I'm not sure exactly what those are. Honestly I'm for whatever works in the end. Most of the select/fetch/build phases are independent of this anyway and that was what I was good at; we are seeing my limitations now. |
@jtpalmer, feel like helping out on this? |
I haven't been following Alien::Base development as closely as I was, so I don't think I'd be much help at this point. Have you already discussed anything with @jberger ? I think the issues I was experiencing may have been resolved. |
Two challenges with this are
For autotool packages the first can be accomplished by passing For the linker there are three approaches that I can think of
This is tricky to fix at the Alien::Base level since the |
One advantage of using static libraries is that This also works nicely in that |
With the new |
For me the key goal is to make things work, regardless of ideas of "elegance". Let us keep pressing forward, making things work! |
Just a thought, but is there a reason static libraries aren't supported. I've been looking at a couple non-Alien::Base Alien:: modules and they specifically only build static libraries. I might be wrong, but static libraries would not need the need run-time provision mentioned in the documentation. This is advantageous since the Alien module would no longer be a run-time requirement.
The text was updated successfully, but these errors were encountered: