Re: Carbon Framework dependancy, .h visibility
Re: Carbon Framework dependancy, .h visibility
- Subject: Re: Carbon Framework dependancy, .h visibility
- From: Fritz Anderson <email@hidden>
- Date: Tue, 31 Jul 2007 07:19:57 -0500
On 31 Jul 2007, at 3:31 AM, Hado Hein wrote:
Do I have to add the relevant headers from the framework by hand?
I tried adding a user header search path of @executable/../Libraries
paired with #include "name.framework/Headers/header1.h" but it didn't
work.
When the framework is added to your project, Xcode will issue the
necessary compiler switches to find the headers and libraries. The
#include should be of "name/header1.h" .
@executable doesn't have any meaning as far as I know.
@executable_path is an instruction to the dynamic loader (at runtime)
to search for the library .dylib at a location relative to the main
binary being linked.* It has no effect when compiling source. Even if
it did, it would make no sense to search relative to the final product
of your target.
— F
* Others: It's more than that, isn't it? The documentation refers to
@executable_path and @loader_path as macros that can locate any
resource. Does this mean that file-system calls can use these macros
in path names, and they'll be patched (at load time or run time?) to
expand to the full path?
_______________________________________________
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