• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Carbon Framework dependancy, .h visibility
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Carbon Framework dependancy, .h visibility


  • Subject: Re: Carbon Framework dependancy, .h visibility
  • From: "Kyle Sluder" <email@hidden>
  • Date: Tue, 31 Jul 2007 10:11:04 -0400

Actually the docs say you should use `` #include
<FrameworkName/HeaderFileName.h> '', but that distinction doesn't
really matter on GCC < 4.0.

The install name of the library is inserted straight into the
executable.  I think the term "resources" might be overloaded,
depending on what layer of the OS we're talking about.  As far as Mach
is concerned, when it's loading code and it's told to look for
"@executable_path/something...", it replaces the text macro
accordingly.

--Kyle Sluder

On 7/31/07, Fritz Anderson <email@hidden> wrote:
> 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
>
 _______________________________________________
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

References: 
 >Carbon Framework dependancy, .h visibility (From: email@hidden (Hado Hein))
 >Re: Carbon Framework dependancy, .h visibility (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: Carbon Framework dependancy, .h visibility
  • Next by Date: Re: Control initialised data layout?
  • Previous by thread: Re: Carbon Framework dependancy, .h visibility
  • Next by thread: How do I include Python.framework?
  • Index(es):
    • Date
    • Thread