Re: Unstuffing my build
Re: Unstuffing my build
- Subject: Re: Unstuffing my build
- From: Graham Cox <email@hidden>
- Date: Tue, 29 Jun 2010 10:52:15 +1000
On 29/06/2010, at 1:39 AM, Kyle Sluder wrote:
> Don't be so sure. 10.6 broke OmniOutliner 3 because it only shipped
> with a newer version of libxslt than the one we were linking with.
>
> It would be a liability for Apple to continue shipping old,
> potentially buggy or security-compromised versions of every dylib.
>
> You'll just have to test your app with the OS seeds. Makes that $99
> for the developer program very much worth it.
Isn't there a way to link against the "latest", whatever it is? Since there's a symlink for that, at least there's an access point in the file system. I realise that it still has to resolve the specific symbols I link against, but they are likely to exist in a newer version and at least I'm no worse off if it fails. Would it be a case of simply renaming the dylib stub to match the symlink?
--Graham
_______________________________________________
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