Re: Build setting for embedded dylib?
Re: Build setting for embedded dylib?
- Subject: Re: Build setting for embedded dylib?
- From: Kyle Sluder <email@hidden>
- Date: Wed, 27 Feb 2013 19:03:42 -0800
On Feb 27, 2013, at 6:53 PM, Graham Cox <email@hidden> wrote:
> Hi all,
>
> I have a private dylib that my app links to. This dylib is copied into the app's bundle (at the moment into /Frameworks, this might be the wrong place), but at runtime this isn't found, as it appears to be searching in /usr/local/lib/.
>
> What setting do I need to add to ensure that at runtime my app's executable searches in the right place for the dylib? I tried setting the Runpath Search Path to a @executable relative path, but that didn't work. I couldn't find the answer in the documentation.
1. Did you actually verify that you're setting the install name of the dylib to the correct value?
2. You should probably use @rpath instead of @executable_path.
Do read Mike Ash's blog post on the topic of install name. It's a bit terse, but it's useful: http://www.mikeash.com/pyblog/friday-qa-2009-11-06-linking-and-install-names.html
--Kyle Sluder
_______________________________________________
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