Re: Embedded Library in Cocoa App
Re: Embedded Library in Cocoa App
- Subject: Re: Embedded Library in Cocoa App
- From: Charles Srstka <email@hidden>
- Date: Thu, 19 Jan 2012 15:31:55 -0600
On Jan 19, 2012, at 3:25 PM, Jens Alfke wrote:
> You can avoid having to set that variable if you change the dylib’s install name — that way targets that link against it will remember a more appropriate path, like a relative path. You can use “@executable_path” in which case the library will be looked for in the same directory as the executable. You can do this in Xcode in the build settings for the library, or you can also edit the copy of the library you include in your app, via a build script — I don’t know exactly what tool is used to edit the install name, but I’m guessing libtool.
If you don’t need to be compatible with OS X 10.4 or earlier, @rpath is probably a better way to go than @executable_path.
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