Re: @executable_path related question (solved)
Re: @executable_path related question (solved)
- Subject: Re: @executable_path related question (solved)
- From: Vyacheslav Karamov <email@hidden>
- Date: Fri, 25 Mar 2011 17:11:33 +0200
24-Mar-11 15:36, Vyacheslav Karamov пишет:
24-Mar-11 15:03, Christiaan Hofman пишет:
On Mar 24, 2011, at 13:58, Vyacheslav Karamov wrote:
Hi All!
I have written IB 3.2.6 plug-in, but it's loaded under XCode
debugging session only.
My plug-in has dependencies such as
@executable_path/../Frameworks/СLControls.framework/Versions/A/СLControls
but how @executable_path will be expanded when it is loaded under
Interface Builder?
This is always expanded to the location of the launched executable
itself, so in this case that of IB. If you want to have a path
relative to the executable that loads an embedded framework (i.e.
your plugin), you should use @loader_path instead.
Christiaan
Thank yo for urgent help.
But what if I have more complicated dependency tree?
I.e.
1) plug-in depends on CLControls.framework, CLKeymapper.framework,
CLCommon.framework
2) CLControls.framework depends on CLKeymapper.framework,
CLCommon.framework, libKeymapTables.dylib
3) CLKeymapper.framework depends on libKeymapTables.dylib,
CLCommon.framework
I've solved this problem by changing $(INSTALL_PATH) of all dependencies
to $(USER_LIBRARY_DIR)/Frameworks, rebuilding them and then copying to
~/Library/Frameworks. I'm confused, because as far as I know, system
must check
/Library/Frameworks,
/Network/Library/Frameworks,
/System/Library/Frameworks
_______________________________________________
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