• 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: time.h vs Time.h
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: time.h vs Time.h


  • Subject: Re: time.h vs Time.h
  • From: Jim Ingham <email@hidden>
  • Date: Fri, 27 Aug 2004 14:37:44 -0700

I am pretty sure the header map is there to handle cases like building a new version of the AppKit framework on a system that already has one installed. In that case, you need to make sure that you pick up the headers from the NEW AppKit frameworks - which are local - and not the system ones, even though the includes are all through <> type includes. So I think the sort of rule you are suggesting would defeat the header map's main purpose.

Jim

On Aug 27, 2004, at 2:22 PM, Massimo Marino wrote:

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.
_______________________________________________
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.


  • Follow-Ups:
    • Re: time.h vs Time.h
      • From: Massimo Marino <email@hidden>
    • Re: time.h vs Time.h
      • From: Markian Hlynka <email@hidden>
    • Re: time.h vs Time.h
      • From: Massimo Marino <email@hidden>
References: 
 >time.h vs Time.h (From: Massimo Marino <email@hidden>)
 >Re: time.h vs Time.h (From: Keith Ray <email@hidden>)
 >Re: time.h vs Time.h (From: Massimo Marino <email@hidden>)
 >Re: time.h vs Time.h (From: Shawn Erickson <email@hidden>)
 >Re: time.h vs Time.h (From: Massimo Marino <email@hidden>)
 >Re: time.h vs Time.h (From: Eric Albert <email@hidden>)
 >Re: time.h vs Time.h (From: Eric Albert <email@hidden>)
 >Re: time.h vs Time.h (From: Massimo Marino <email@hidden>)
 >Re: time.h vs Time.h (From: Massimo Marino <email@hidden>)

  • Prev by Date: Re: time.h vs Time.h
  • Next by Date: Re: time.h vs Time.h
  • Previous by thread: Re: time.h vs Time.h
  • Next by thread: Re: time.h vs Time.h
  • Index(es):
    • Date
    • Thread