• 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: Eric Albert <email@hidden>
  • Date: Thu, 26 Aug 2004 23:31:41 -0700

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.


Hope this helps,
Eric
_______________________________________________
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: Eric Albert <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>)

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