• 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: [Config Files] What can I really modify in a config file?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Config Files] What can I really modify in a config file?


  • Subject: Re: [Config Files] What can I really modify in a config file?
  • From: Scott Tooker <email@hidden>
  • Date: Wed, 1 Mar 2006 14:37:28 -0800

On Mar 1, 2006, at 12:00 PM, Rush Manbert wrote:

I'm testing this using Xcode 2.2.1.

I tried setting PRODUCT_NAME in my config file, but it had no effect. I tried clearing the value for PRODUCT_NAME in the dialog so that my config file could rule, but that gives an error when you change it, and again at build time, saying that $(PRODUCT_NAME) is undefined (despite what's in my config file).

This lead me to look at ZERO_LINK behavior. It seems that it doesn't matter what I put in my config file. Whatever is specified in the dialog is what happens. If my config file says NO but the dialog has it checked, Zero Link is on. If my config file says YES but the dialog has it not checked, then Zero Link is off. If the config file and the dialog agree, then I get what I expect, but it's still whatever the dialog says.

If the basic rule is that the build settings dialog overrides the config file, then this makes sense, but it seems to make the build setting management be a total PITA.

So, a question for the Apple employees. Is this the expected behavior? If so, is there any way to tell the build system to ignore the dialog?
What build settings can I specify in a config file and really expect them to influence the build?

You can specify any build setting in a Config file and it will be honored if the target or project doesn't override it. If you want to manage all your build settings directly in a config file you can set the target (or project) to use a config file and then delete all the customized build settings. Then there will be no target-level settings to override the configuration file.


This gets a little more subtle when you want to provide a set of settings to apply across the entire project, but then customize the settings of a given target, but the same idea applies (make sure that the project uses the proper config file and then remove any customized build settings in the project).

Scott



Thanks, Rush _______________________________________________ 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

_______________________________________________ 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: [Config Files] What can I really modify in a config file?
      • From: Rush Manbert <email@hidden>
    • Re: [Config Files] What can I really modify in a config file?
      • From: Thomas Engelmeier <email@hidden>
References: 
 >[Config Files] What can I really modify in a config file? (From: Rush Manbert <email@hidden>)

  • Prev by Date: Re: Easily reproducible XCode editor hang
  • Next by Date: "multiple definitions of symbol" - warning or error?
  • Previous by thread: [Config Files] What can I really modify in a config file?
  • Next by thread: Re: [Config Files] What can I really modify in a config file?
  • Index(es):
    • Date
    • Thread