> On 12/01/2009 06:04 PM, Jonas Thiem wrote: > > This topic is rather old, and I'm referring to a particular post which > > can be found here: > > http://www.mail-archive.com/libtool@gnu.org/msg03642.html > > Obviously it isn't possible to link a static lib from a shared lib > > compiled in libtool as libtool blocks it (technically it would be > > possible on many, but not all platforms). This affects all platforms > > including Windows, not just Mac OS X. > > > > Robert Boehne suggested some solutions to this: > > > Suggestion 1, you could link to shared libraries rather than archives. > > >Suggestion 2, if you're building it yourself, make the static libs > > >convenience libraries, this will have the same effect as linking to > > static libs, but is portable. > > This should work, we changed the dep libs check method to pass_all, if > you are using libtool-1.5 (April 2003) or later, you shouldn't see a > problem on Mac OS X. > > Peter > -- > Peter O'Gorman > http://pogma.com >
For windows targets it doesn't work at all (compiling on a linux machine with i486-mignw32. I'm also pretty sure my libtool version is newer, but I need to recheck when I'm at home and having access to the machine. The only way to link a static lib for a windows target seems to be not to use libtool (given you cannot move to a convenience lib or a shared lib which is the case for a plugin that references back to the main app's symbol file). ___________________________________________________________ Preisknaller: WEB.DE DSL Flatrate für nur 16,99 Euro/mtl.! http://produkte.web.de/go/02/ _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
