Re: Using libcrypto & the 10.6 SDK with a minimum OS requirement of 10.5
Re: Using libcrypto & the 10.6 SDK with a minimum OS requirement of 10.5
- Subject: Re: Using libcrypto & the 10.6 SDK with a minimum OS requirement of 10.5
- From: Jean-Daniel Dupas <email@hidden>
- Date: Sat, 19 Sep 2009 11:58:56 +0200
Le 19 sept. 2009 à 01:13, Jens Alfke a écrit :
On Sep 18, 2009, at 3:48 PM, Jim Correia wrote:
If I like to libcrypto, this records libcrypto.0.9.8 in the binary,
which then won't launch on 10.5.
You should link to libcrypto.dylib (the symlink), not to the actual
version-numbered dylib. That way the symlink will resolve to the
right library on different platforms.
IIRC there was (is?) an Xcode bug where if you added a symlink to
the project it would 'helpfully' resolve it for you, causing this
sort of problem. I'm not sure whether this is fixed. What UI did you
use to add the library to the project?
It won't. If you link on the symlink using 10.6 SDK, the install path
of the library in you executable will be libcrypto.0.9.8.dylib which
do not exists on 10.5.
You should copy the libcrypto from the 10.5 SDK in your project and
link your executable on this file.
Note that you don't have to distribute this file, just putting it
somewhere the linker can find it, so your executable will use the
system's libcrypto.0.9.7.dylib.
An easy way to avoid link path resolution order when you do this is to
simply rename the lib you want to use (to libmycrypto.dylib for
example) and then drop this library in your project. As the linker use
the install name which has nothing to do with the actual file name, it
will not be an issue for deployment.
-- Jean-Daniel
_______________________________________________
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