• 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: Occasional failure to find system headers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Occasional failure to find system headers


  • Subject: Re: Occasional failure to find system headers
  • From: John Brownie <email@hidden>
  • Date: Sun, 18 May 2008 09:19:52 +1000
  • Organization: SIL

On 18/5/08 02:02 Chris Espinosa wrote:

This build command doesn't give gcc any path to find any system headers. Without it, #include < > statements aren't going to work.

...

This successful gcc command passes a Header Search Path pointing to the SDK's "FlatCarbon" directory, which is just a bunch of files that redirect into the SDK's /System/Library/Frameworks directory. This will work for frameworks used by Carbon applications, but it is not updated to new frameworks introduced after Mac OS X 10.3.

You should probably ensure that /System/Library/Frameworks is in your Frameworks Search Path (it'll get redirected to the proper SDK automatically).

Hmm, the Frameworks Search Path is blank. The FlatCarbon directory is specified in the Header Search Paths option. The weird thing is that it gets left out once, and then re-added after the clean. No change happens to the project options, so it's likely a bug in Xcode. I'm not sure that I can get it reproducible for filing as a bug, though.


If I remove FlatCarbon from the Header Search Paths, and add /System/Library/Frameworks to Frameworks Search Path, it fails to compile. I am guessing that this means I would need to update all my include statements to be framework style includes. Is that correct?

As you can tell from the transcript, it's a converted PowerPlant project, so I'm using a version of PP_Xcode.h in my precompiled header. If I modify that to include <Carbon/Carbon.h> or some combination of frameworks, will it solve the majority of my problems?

John
--
John Brownie, email@hidden or email@hidden
Summer Institute of Linguistics      | Mussau-Emira language, Mussau Is.
Ukarumpa, Eastern Highlands Province | New Ireland Province
Papua New Guinea                     | Papua New Guinea
_______________________________________________
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


  • Follow-Ups:
    • Re: Occasional failure to find system headers
      • From: Chris Espinosa <email@hidden>
References: 
 >Occasional failure to find system headers (From: John Brownie <email@hidden>)
 >Re: Occasional failure to find system headers (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: (objc_warning) is valid for ObjC/ObjC++ but not for C
  • Next by Date: RE: Books?
  • Previous by thread: Re: Occasional failure to find system headers
  • Next by thread: Re: Occasional failure to find system headers
  • Index(es):
    • Date
    • Thread