Re: Chicken & egg situation
Re: Chicken & egg situation
- Subject: Re: Chicken & egg situation
- From: Jean-Daniel Dupas <email@hidden>
- Date: Thu, 26 Jun 2008 18:21:19 +0200
Le 26 juin 08 à 18:12, Timothy Reaves a écrit :
I'm writing an IB plugin for a custom control. I used the XCode
templete, and everything works O.K. if I install the framework for
the custom control in /Library/Frameworks. However, I'd like this to
be an embedded framework, as the apps that use it shouldn't have to
install to the machine framework directory. For a normal framework,
this isn't an issue; you just change the execution path in the target
settings. But this doesn't work for a custom control.
The issue is that the CustomControl.ibplugin bundle needs to
reference the framework too. This leads to all kinds of issues, but
basically the ibplugin bundle can't load, saying it can't load the
library at @executable_path/../frameworks/(the rest of the path).
But if I change the executable path in the framework back to the
default, and put the framework into the machine's default location,
it works.
Another issue is build order; the framework needs to include the
ibplugin bundle so that IB will automagically find & load it, and the
ibplugin needs the framework. So if you follow the docs and put the
items in the standard targets, you have to hit the build button a
couple of times for it to successfully complete, as binaries that are
referenced are not yet there until a later build phase, etc.
So two questions:
*) can an IB plugin use an embedded framework?
*) to get around the build order issue, do I have to resort to adding
another target that copies the varies pieces to the correct location?
Thanks.
I think using @loader_path instead of @executable_path may solve your
problem.
@loader_path define the path relatively to the "loader", whatever it
is (bundle, executable).
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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