Re: Plugin linking to private framework
Re: Plugin linking to private framework
- Subject: Re: Plugin linking to private framework
- From: Chris Hanson <email@hidden>
- Date: Thu, 20 May 2010 18:59:49 -0700
On May 20, 2010, at 2:29 PM, email@hidden wrote:
> My app uses @rpath to enable linking of plugin bundles + auxiliary executables to various private application frameworks.
[…]
> Presumably, for a plugin that is loaded from an alternate location(s), all that can be done is to include something like:
>
> /Applications/MyApp/Contents/Frameworks
>
> in the external bundles rpath search, in the knowledge that if the app is moved elsewhere the plugin will fail to find the private framework.
Use @executable_path/../Frameworks as a runpath search path when linking both the plug-ins and the executable. @executable_path is the path to the executable for the process, @loader_path is the path to whatever loaded a binary by linking against it.
— Chris
PS - Plug-in has a hyphen, see its definition in the Apple Publications Style Guide, page 135. ;) <http://developer.apple.com/mac/library/documentation/UserExperience/Conceptual/APStyleGuide/APSG_2009.pdf>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden