• 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: A Few (Probably) Simple Questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A Few (Probably) Simple Questions


  • Subject: Re: A Few (Probably) Simple Questions
  • From: Scott Thompson <email@hidden>
  • Date: Thu, 5 Aug 2004 09:23:13 -0500

Is it ever the case that a target-level setting overrides a project-level setting?

I don't believe so. The build style setting always trumps the target setting.


future GUI suggestion: How about showing side-by-side columns for Project Level settings and each of the Target level settings, and bold-face the one that overrules the others?

You can do this now. Show the build inspector for a target and show the collections drawer. Click on any item in the drawer and then select all. The list in the inspector now shows all settings. The ones with lines through them are being overruled by the build style.


It only works for one target at a time but that should be enough for 99.9% of cases.

I took some notes on this at WWDC. I think it will be OK to share it since it deals with public releases of XCode. Please realize that I scrawled this list down in a darkened lecture hall and rather quickly so it may not be 100% accurate. Anyway, what I have written down is that the precedence order is:



Command line arguments (to xcodebuild) Build style settings Target Settings built-in defaults environment

As I recall, what this list reprsents is the precedence order of settings. In other words, if you provide a setting on the command line for xcode build it will take precedence over the build style settings. Build style settings, in turn, take precedence over target settings. The target can override the "built-in" default settings. Finally, the environment variables (presumably that XCode was started under?) are used as a last resort.

The only reason I mention it is because during the session it occurred to me that I had never use xcodebuild so I hadn't thought about the role that command line arguments might play. Coming from the Mac OS 9 camp I had also never given much thought to the way that environment variables factor in.

Kinda nifty.

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


References: 
 >A Few (Probably) Simple Questions (From: Lance Drake <email@hidden>)
 >Re: A Few (Probably) Simple Questions (From: Frank Midgley <email@hidden>)
 >Re: A Few (Probably) Simple Questions (From: Keith Ray <email@hidden>)
 >Re: A Few (Probably) Simple Questions (From: Frank Midgley <email@hidden>)

  • Prev by Date: Re: Xcode does seem hard on newbies(was Xcode release notes)
  • Next by Date: Re: Xcode does seem hard on newbies(was Xcode release notes)
  • Previous by thread: Re: A Few (Probably) Simple Questions
  • Next by thread: Re: A Few (Probably) Simple Questions
  • Index(es):
    • Date
    • Thread