Re: Loadable bundles and common files
Re: Loadable bundles and common files
- Subject: Re: Loadable bundles and common files
- From: Rudi Sherry <email@hidden>
- Date: Wed, 10 Nov 2004 16:10:26 -0800
On Nov 8, 2004, at 11:27 AM, Christian Schneider wrote:
You'll have to set the bundle's path to
@executable_path/...blahblah..., as with any embedded framework. I'm
not sure, though, whether the @executable_path is the current
application, or whether it is the library in the case of a framework.
So it may not be possible at all. But I think it was the app's path
that is used in that case.
OK thanks, I'll fiddle around a bit until it fits.
@executable_path is based off the current application, always. We have
a loadable wrapper framework that uses other (private) frameworks, and
since we don't want all applications to have access to our other
frameworks, we can't put them in the usual places (/Library/Framework
or ~/Library/Frameworks). Instead we have to create symlinks to them
inside the application that loads our wrapper framework (even though
it's not our application). It's not pretty and can cause some problems
with limited users.
I've heard rumors that there is some sort of fix for this in Tiger.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden