Re: Unstuffing my build
Re: Unstuffing my build
- Subject: Re: Unstuffing my build
- From: Michael Ash <email@hidden>
- Date: Mon, 28 Jun 2010 10:58:15 -0400
On Mon, Jun 28, 2010 at 6:09 AM, Graham Cox <email@hidden> wrote:
>
> On 28/06/2010, at 7:40 PM, Graham Cox wrote:
>
>> I recently switched my project from using the 10.5 Base SDK to the 10.6 SDK (but with minimum deployment target 10.5).
>>
>> My project links to libcrypto by adding -lcrypto to "Other Linker flags". This has never previously given me a problem.
>>
>> Now my app won't launch on 10.5, because /usr/lib/libcrypto.0.9.8.dylib image not found. (10.5 has 0.9.7, and also a symlink to that just called libcrypto). How has this specific version got written into my executable? How can I fix it?
>
>
> OK, I found something on this in the list archives. Numerous solutions were suggested but I've gone with copying the libcrypto.0.9.7.dylib stub from the 10.5 SDK into my project. (A better-sounding option would be to use CommonCrypto but unfortunately one bit of my code uses RSA, which isn't in CC apparently).
>
> Is this approach going to be safe in the future? What if Apple don't include this version in future OS releases?
If Apple broke it, they would break every single app built against the
10.5 SDK, so I think you're pretty safe.
Mike
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden