On Aug 22, 2011, at 9:06 AM, Matthias Melcher wrote: > On 22.08.2011, at 17:54, Michael Sweet wrote: > >> On Aug 22, 2011, at 12:25 AM, Matthias Melcher wrote: >>> >>> OK, I made a design decision here that will haunt me for a while. I figured >>> it would be useful to compile jpeg, png, and zlib from scratch always. >> >> Note that this will *not* work for Mac OS X since a lot of the system >> libraries link against the supplied zlib - you'll find a configure test >> explicitly to prevent --enable-local-zlib on Mac OS X that we've had since >> FLTK 1.1.x... > > Oh? Will that give naming conflicts? The command line version currently works > AFAIKT (maybe *because* of the messed up link order), but I have not finished > the Xcode setup yet.
My guess is that the current Xcode tools are preferring the system zlib over the local one, or it could be a link order thing (and you are just "lucky" right now), but I know from experience that you can't override the system-supplied zlib and still link against ApplicationServices, Foundation, or CoreFoundation and get a stable (or even functioning) executable, particularly for a shared library setup where parts of libfltk_z.a are part of libfltk.dylib. ________________________________________ Michael Sweet, Easy Software Products _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
