* Ralf Wildenhues wrote on Fri, Sep 08, 2006 at 08:36:54AM CEST: > I recommend that if libgnu.a needs symbols from other libraries, then it > should provide a macro $(LIBGNULIB) or so, that programs can use to link > against, and that it should then contain those additional libraries. > This way, it is possible for the program to link against shared > libraries of those; instead pulling archive members of, say, libiconv.a, > into libgnu.a seems rather ugly to me. (If that's what you're doing > currently, that is.)
In case that wasn't clear, I think I should point out that the above should not be done for libtool libraries: in that case, libtool will push the dependencies itself through storing them in libgnu.la (in the static case) or linking libgnu.so against whatever it needs (in the shared case). The latter is necessary for systems that do not allow undefined symbols in shared libraries. Cheers, Ralf
