• 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: New to Xcode and need help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New to Xcode and need help


  • Subject: Re: New to Xcode and need help
  • From: Scott Tooker <email@hidden>
  • Date: Thu, 23 Jun 2005 12:56:04 -0700


On Jun 23, 2005, at 11:40 AM, Bryan Pietrzak wrote:


On Jun 22, 2005, at 12:38 PM, Scott Tooker wrote:


A better solution to try (which is documented in Help->Show Build Settings Notes for Xcode 2.1) is USE_SEPARATE_HEADERMAPS:

USE_SEPARATE_HEADERMAPS

If set to YES, project headers will only be accessible with #include "header.h"-style preprocessor directives. The default in Xcode is that both #include <header.h>-style and #include "header.h"-style directives will search the project’s paths before system paths, with the consequence that project headers (such as your own String.h header) would have precedence over system headers.

USE_SEPARATE_HEADERMAPS does not have a standard build setting entry; you must add it as a custom build setting to the target or project configurations that need it. This setting is used only for GCC 4.0 and later.


This kind of thing is what I find somewhat frustrating about Xcode. Some things just are not very discoverable. You MUST read and search documentation, and lots of it, to build what seems like straight-forward projects sometimes. That's not very mac-like. Thankfully the documentation IS improving. But still... this is a mac app :)


Personally, I feel that *every* option like the above should be available in the GUI as a checkbox or whatever is appropriate. Having to to hunt down things like this is very wasteful of time and resources.... IF you are even aware that something might be able to be set like this to even begin searching for it.

Just my two cents. I know you guys are doing well, but I'd love to hear someone say that you have a new team policy: NO new compiler/ lnker/etc settings unless available as GUI options as well.

Taking the stand that all compiler/linker/tool settings HAVE to have associated UI is just not feasible, there are just too many flags and settings out there. We do try to make the commonly use or important settings visible in the UI. In the case above, the desire was to have the behavior on by default (and therefore not need custom UI for the setting), but we didn't get there for Xcode 2.1.



Bryan



_______________________________________________ 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
  • Follow-Ups:
    • Re: New to Xcode and need help
      • From: "Sean McBride" <email@hidden>
    • Re: New to Xcode and need help
      • From: Bryan Pietrzak <email@hidden>
References: 
 >New to Xcode and need help (From: RC <email@hidden>)
 >Re: New to Xcode and need help (From: Scott Tooker <email@hidden>)
 >Re: New to Xcode and need help (From: Bryan Pietrzak <email@hidden>)

  • Prev by Date: Developer Transition System - distributed builds
  • Next by Date: Re: Developer Transition System - distributed builds
  • Previous by thread: Re: New to Xcode and need help
  • Next by thread: Re: New to Xcode and need help
  • Index(es):
    • Date
    • Thread