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: "email@hidden" <email@hidden>
- Date: Sat, 19 Sep 2009 17:38:56 +0100
On 19 Sep 2009, at 17:32, Jens Alfke wrote:
On Sep 19, 2009, at 2:58 AM, Jean-Daniel Dupas wrote:
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.
Really? This still sounds like an Xcode bug to me. I thought the
whole reason for having the multiple library symlinks in /usr/lib
was so that binaries could link against the generic library name and
have it resolve to the current version at runtime (as is done with
the library symlinks inside frameworks.)
That sounds like it should be the way it works - but it doesn't seem to.
I think you can work around this by, instead of adding the library
file to the project, just adding a linker flag to the target build
settings, like "-lcrypto". That should force it to record the
generic name in the output binary.
My app was using this approach on 10.5. When I tried to cross develop
on 10.6 it linked to 0.9.8 and broke the app on 10.5
—Jens _______________________________________________
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
Jonathan Mitchell
Developer
http://www.mugginsoft.com
_______________________________________________
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