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: Greg Hurrell <email@hidden>
- Date: Fri, 3 Mar 2006 05:19:16 +0100
El 02/03/2006, a las 23:42, Rush Manbert escribió:
Thanks Greg. I had read the section that you referenced. What I had
missed was in the section before that one, called "Build Settings":
http://developer.apple.com/documentation/DeveloperTools/Conceptual/
XcodeUserGuide/Contents/Resources/en.lproj/05_04_bs_build_settings/
chapter_31_section_5.html
In particular, the sentence:
"When you base a build configuration on a configuration file, Xcode
sets the default specifications of the build settings in the build
configuration to the corresponding specifications in the
configuration file."
This explains a question I posed in a subsequent post. When you
select the config file, the values in the inspector are supposed to
change to reflect what is set by the config file.
The behaviour is actually quite consistent once you get used to it.
Xcode is doing exactly what the sentence you quoted says: setting the
*default* settings (ie. those which have no custom or overridden
setting); you won't see any change in the custom/overridden settings.
Basically anything that appears in BOLD text in any build settings
dialog is a custom override and will *never* get automatically
deleted or overridden by Xcode, even when you select a new config
file. If you select a new config file, everything EXCEPT the
overrides (in bold) will inherit the new settings. In order to get
even the overridden values to inherit from the config file you'll
need to delete the custom overrides, using the delete key.
Needless to say, if you see a BOLD setting at the project level that
means it's overridden at the project level. If you see a BOLD setting
at the target level that means it's overridden at the target level. A
setting can appear BOLD at both, one, or none of the two levels, and
each combination means a different thing (but all very logical once
you understand it).
If you design your config files thoughtfully you'll find that you
need very few custom overrides at all, pretty much just PRODUCT_NAME
and little else.
Cheers,
Greg
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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