Re: Occasional failure to find system headers
Re: Occasional failure to find system headers
- Subject: Re: Occasional failure to find system headers
- From: Chris Espinosa <email@hidden>
- Date: Wed, 21 May 2008 10:08:15 -0700
On May 17, 2008, at 4:19 PM, John Brownie wrote:
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?
That's correct. FlatCarbon exists to aid transition of older code
from Mac OS 9 (8,7,6) UniversalHeaders to framework-style headers.
Either keep the #include <MacErrors.h> and FlatCarbon, or move to
#include <Carbon/Carbon.h> and add /S/L/F to your Frameworks Search
Path and remove FlatCarbon from your Header Search Path.
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?
It might, but it depends on how every single source and header file is
written. Even one System 7-style #include will cause your build to
break if you remove FlatCarbon.
Chris
_______________________________________________
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