Re: 10.6 SDk and 10.5 Deployment
Re: 10.6 SDk and 10.5 Deployment
- Subject: Re: 10.6 SDk and 10.5 Deployment
- From: Charles Srstka <email@hidden>
- Date: Thu, 28 Jun 2012 23:38:26 -0500
On Jun 28, 2012, at 4:19 PM, Kyle Sluder wrote:
> On Jun 28, 2012, at 1:58 PM, Eric Wing <email@hidden> wrote:
>
>>
>> One additional gotcha that I have hit multiple times is that if your
>> application links to system .dylibs (not .frameworks), Xcode links to
>> the explicit filename versioned .dylib file on your system that the
>> generic one is symlinked to. This is a problem if say 10.6 has a newer
>> version of libcrypto.dylib or libreadline.dylib which doesn't exist on
>> 10.5. Your app will crash on launch on 10.5 because it can't find the
>> dependent library. For this, I have resorted to using
>> install_name_tool to rewrite the dependencies to link to the generic
>> symlinked version because Xcode has fought all my attempts to control
>> what it actually links to.
>
> Be careful! There could be binary incompatibilities between the two versions of the dylib—sometimes even between point revisions! We got bit by this in the 10.5->10.6 transition.
My current solution to this is to stash a copy of the dylibs that I need for whatever OS in a folder somewhere, and then adding "-L/path/to/custom/dylibs/folder -lwhatever” to Other Linker Flags in the build settings, and leaving the dylib out of Xcode’s link phase.
Charles
_______________________________________________
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