On Sun, 22 Jan 2006 10:59:49 -0500, "Pierre Thibault" <email@hidden>
wrote:
>> > 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.
>
> The @loader_path is really what I needed. It solves all my problems. Thank
you!
>> > 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...
>
> Me too! But have you tried with a bundle? It does not work for Bob, the person
> who asked Bob and neither for me. So, can you try and tell me?
All my applications are bundles and I very commonly utilize plug-in's &
frameworks built with @executable_path install paths. Note that in all these
cases the "executable" is the application and the dylib I'm loading is
relative to that.
If you have dylibs that load dylibs that are located relative to it but not
in any specific (system? or app?) location then "@loader_path" is the
correct solution.
--
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
