Re: Link to zlib
Re: Link to zlib
- Subject: Re: Link to zlib
- From: Fritz Anderson <email@hidden>
- Date: Wed, 11 Jun 2008 14:17:03 -0500
On 11 Jun 2008, at 1:56 PM, Nick Zitzmann wrote:
That was good advice back when Xcode would resolve symbolic links to
libraries (incorrect behavior) rather than pointing the linker to
the symbolic link (correct behavior). That bug was fixed a long time
ago, and now it doesn't really matter.
This is being hashed out in a thread on cocoa-dev, which has diverted
into strategies for using weak links, so I don't have a hook there to
ask this.
The assertion is that if you link, for instance, to /usr/lib/
libcurl.dylib, that that symlink will be the very path used for the
load path.
But if I build a Hello World, and add /usr/lib/libcurl.dylib, using
SDKROOT for 10.5 and MACOSX_DEPLOYMENT_TARGET to 10.3, I get these
load paths:
$ otool -L /Users/fritza/Projects/BuildProducts/Debug/KillMeSymLinkLib
/Users/fritza/Projects/BuildProducts/Debug/KillMeSymLinkLib:
/usr/lib/libcurl.4.dylib (compatibility version 5.0.0, current
version 5.0.0)
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version
47.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.0.0)
- The load path is not /usr/lib/curl, but the resolved symlink.
- The application won't launch on 10.3, which doesn't have /usr/lib/
libcurl.4.dylib.
Xcode 3.0, Mac OS X 10.5.3.
Am I missing something?
— F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden