Re: [Config Files] What can I really modify in a config file?
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: Rush Manbert <email@hidden>
- Date: Thu, 02 Mar 2006 11:32:48 -0800
Scott Tooker wrote:
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,
The behavior I observe in my test project does not agree with your
statement. I have no config file specified at the project level, only
the target. Zero Link is not checked at the project level. No matter
what I put into my config file at the target level, Zero Link on/off is
controlled by the state of the checkbox in the target build settings dialog.
I just made a brand new test project to verify this behavior. I made
screen shots, but they're too big to attach.
Either I don't understand something, or my config file has no effect on
the Zero Link build setting and there is no way to "delete" or "remove"
any build setting that is controlled via a checkbox. I'm hoping that
this is a misunderstanding on my part.
I won't get into the issues with PRODUCT_NAME, other than to say that I
made a new project that verifies what I said in the original post. I get
an error at build time if it's not defined in the dialog, even if I
define it in the config file.
- 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