> George Warner wrote:
> I found some answer to my problem. Here at Bob, from Omnigroup, as to
> say:
>
> -----------------------------------------
> You can't, dyld doesn't support a relative reference to a loading
> bundle. Basically, you can load it from a known place (forcing the
> user to install your bundle in a particular place), build+link your
> libraries statically, or use the NSBundle/dyld APIs yourself and get
> references to the symbols you use (can be a pain, but entirely
> possible).
> -----------------------------------------
> [...]
> If you have something better, just tell me.
You can also locate resources relative to the location of a library using
@loader_path at the beginning of the path. This means that regardless of
where a library is located, code within it can locate resources based on the
location of the library. With this feature, you can, for example, create
nested frameworks (frameworks of frameworks). You don¹t have to place
related libraries in a specific location to be able to share resources
between them.
> George Warner wrote:
>> Can you post you "otool -L" output? Maybe it won't "look fine" to us.
> ;-)
>
> Well, if Bob is right, I believe he is, I just can't use
> @executable_path in a bundle and I must use absolute paths.
I do this all the time and don't have a problem...
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
