Re: Building all static

[Peter O'Gorman]

Gary V. Vaughan wrote:

> I see.  Maybe that's the same thing then, albeit a different algorithm.
> The problem with doing it that way is this: when libtool encounters a native
> (no .la) shared lib and links it, most modern platforms pull in the deplibs
> automatically AIUI.  This certainly isn't true of static archives, so we
> could breed situations where specifying -static to libtool will break a build
> that was perfectly correct when using shared libraries.

Well, there is bugger all that we can do about that. Yes, I think it is the 
same idea. I say "If libtool sees libfoo.so and libfoo.a in a linker path 
and -static is specified it should put path/to/libfoo.a on the line it sends 
to the linker". Of course, it should do it's platform independent foo, 
looking for the proper shared extension and static extensions.

> As an aside, I notice that lt_prog_compiler_static is not set for branch-2-0
> libtool on my darwin machine.  I guess this is a bug, no?

There is no way to specify -static to the toolchain. There are patches for 
it, including mine at <http://www.pogma.com/misc/Bstaticflag.diff>, but 
Apple has yet to integrate them. So, if you want to file a bug at 
http://bugreporter.apple.com, feel free :-).

Peter
--
Peter O'Gorman - http://www.pogma.com