Re: Linking to third-party Frameworks and dylibs from a plug-in
Re: Linking to third-party Frameworks and dylibs from a plug-in
- Subject: Re: Linking to third-party Frameworks and dylibs from a plug-in
- From: Dan Korn <email@hidden>
- Date: Tue, 11 Mar 2008 02:43:52 -0500
On Mar 11, 2008, at 12:25 AM, Sherm Pendley wrote:
On Mon, Mar 10, 2008 at 10:23 PM, Dan Korn <email@hidden>
wrote:
My only other question is, is there someplace where @executable_path
and @loader_path and any other possible settings are documented? I
looked around but couldn't find anything official.
Here's a good starting point:
http://developer.apple.com/documentation/MacOSX/Conceptual/BPFrameworks/Frameworks.html
Thanks Sherm. That is indeed a great place to learn about Frameworks
in general, but I can't find a single mention of @loader_path anywhere
in that entire section.
In fact, if I search developer.apple.com for "loader_path", I get 21
hits, none in the Framework Programming Guide. Other than that
Leopard release note and a bunch of Document Revision History entries,
the only hits are in the Dynamic Library Design Guidelines and the
Mach-O Programming Topics PDF, the latter of which doesn't actually
say anything about it other than that it some information was
supposedly added in a revision.
The only thing close to a definitive explanation of these macros is on
this page:
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/Articles/DynamicLibraryDesignGuidelines.html
>
Even then, it's not much, certainly not in the context of Frameworks
or even Xcode, and there's no mention of other options I've heard
about only in legend, such as @rpath. Certainly there's no way to
really stumble upon these macros as the solution to the problem I had
without some other resource, such as this list or Google. So, my
question still stands: Is the full set of these macros defined anywhere?
Forgive my late night gripe, but I really want to be able to just link
to my libraries and get on with my project without becoming an expert
in the inner workings of the ABI and the Dynamic Loader. The
transition to Xcode is challenging enough, not to mention dealing with
all the architectural changes, without having to extract tribal
knowledge. Sometimes I really miss programming, and not just shell
scripts to work around limitations in the IDE. Anyway, I'm happy to
have this option available, even if it's not documented as well as it
could be, but this would seem to be an opportunity for improvement in
the doc.
Thanks,
Dan
_______________________________________________
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