Re: /usr/include Still Found Using Mac OS SDKs
Re: /usr/include Still Found Using Mac OS SDKs
- Subject: Re: /usr/include Still Found Using Mac OS SDKs
- From: Chris Espinosa <email@hidden>
- Date: Tue, 6 Jan 2004 23:18:53 -0800
On Jan 6, 2004, at 11:11 PM, Kevin Grant wrote:
Can anyone tell me why Xcode might be finding /usr/include headers
despite my selection of the Mac OS X 10.1 SDK?
I have already thoroughly scrubbed a couple of different inspectors
and found no references to compiler flags or header paths, etc. that
might show /usr/include being referenced...
Try adding -v to your Other C Flags for a target in which this is
happening, and send me the complete build results log (from the
Detailed Build Results window, pull up the split bar at the bottom with
the divot, and copy all the text in there).
The normal reason for this to happen is that gcc has "fallback paths"
when #included files aren't found, and /usr/include is (near the end
of) the fallback list. You can defeat this with -nostdinc, but then
you have to explicitly define $(SDKROOT)/usr/include as a path in all
targets, which is a pain.
Chris Espinosa
Apple
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.