As stated, Mac OS X (any version) never shipped with libjpeg or
libgif inside any folder or subfolder of /usr/.
Because they do not come with Mac OS X, you should not be linking to
libjpeg or libgif.
The OP explicitly stated that he's not linking against them.
If you want to load images and what-not on Mac OS X, use ImageIO.
See http://developer.apple.com/graphicsimaging/
workingwithimageio.html for more information on using ImageIO, the
preferred image file format framework on Mac OS X.
Unfortunately, ImageIO is causing this problem, combined with the new
linker on 10.5; anything that links against ApplicationServices gets
bitten by this. The easiest solution is to compile against the 10.5
SDK with a 10.4 deployment target.
--
adam
On Jan 21, 2008, at 3:25 PM, Marc Lohse wrote:
I still have to say that i am unhappy because libjpeg is not the
only one that i have to bake a fat binary of - after lipo-ing
together
a universal libjpeg, the build fails with libgif causing the same
problem (and i am already expecting more work-causing trouble
of the same kind coming my way from the rest of the occupants
of /usr/local/lib). Is this really the way it's supposed to be?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
