> > I don’t know what the executable_path is for a screensaver, you’d think it > was very much the same thing. So first simplest option is to work out what > that is and then just put the library at the place it expects to be, > @executable_path/../Frameworks/<lots of garbage>. As long as that’s within > your bundle somewhere, trivial to do. You can even put it somewhere else and > put a symlink in the bundle.
The @executable_path for the Screen saver will be the path to the executable process that loads the OP’s screen saver plugin. in this case ScreenSaverEngine. > > If you want to change it to something like @rpath/whatever then > > install_name_tool -id @rpath/whatever <object> This is where I get confused. In my project not the original posters my framework has Installation Directory set to @rpath and everything works as I need it to thanks to that Mike Ash article. But if I do otool -D on the framework then I see @executable_path … etc. Making me conclude the rpath information was stored separately in the binary to the install name so my thinking was that modifying the install name wouldn’t help. Kevin _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
