Re: time.h vs Time.h
Re: time.h vs Time.h
- Subject: Re: time.h vs Time.h
- From: Massimo Marino <email@hidden>
- Date: Fri, 27 Aug 2004 23:22:13 +0200
On Aug 27, 2004, at 11:08 PM, Massimo Marino wrote:
On Aug 27, 2004, at 6:43 PM, Eric Albert wrote:
On Aug 26, 2004, at 11:31 PM, Eric Albert wrote:
On Aug 26, 2004, at 7:33 AM, Massimo Marino wrote:
currently the only workaround I have found is to copy /usr/include
header files referenced by system files locally. Xcode then finds
them instead of digging (without any -I<path> to those files) in
the project files with same names (although starting with a capital
letter, as in SealBase/Time.h).
Try adding
USE_HEADERMAPS = NO
to your target settings. I think this gets Xcode to invoke GCC in a
way that references header files much more like what happens when
you use GCC from the command line.
Oops...I looked up the wrong message in the archives for this. The
correct setting is
USE_HEADERMAP = NO
Sorry about that,
Eric
Eric, BINGO! The correct /usr/include/time.h is picked up.
Thanks
Still, Eric, MHO is that including an header with < > should somehow
force the USE_HEADERMAP=0 somehow for those headers in an automatic
way: Local headers, even in headermap, should never take precedence
over system ones.
Cheers
Massimo
_______________________________________________
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.