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 protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
