On Mar 22, 2005, at 8:21 AM, René Puls wrote: Remove (don't just turn off; select and click the "–" button) the ZeroLink entry in all your build styles. Then you can set it inddividually per target.
Thanks, I guess that will do as a workaround. However, for my main application target, I do want to have the normal behavior where ZeroLink is enabled for Development builds and disabled for the final Deployment build.
I would like to tell Xcode to never enable ZeroLink for one specific target, but keep the default behavior for all other targets. This doesn't seem to be such an unusual situation - should I file a feature request for this?
There's a general technique for doing this that applies to any setting, not just ZeroLink.
- In your Deployment build, set ZeroLink to NO. This ensures that Deployment for all targets is never zero-linked. - In your Development build style, set ZeroLink to $(TARGET_SPECIFIC_ZERO_LINK). This means that the value of Zero Link will be set by that build setting in each target. - Select all targets as a group selection, choose Get Info, go to the Build tab, press "+", and add TARGET_SPECIFIC_ZERO_LINK and set its value to YES. This sets the build setting in all targets. - Then inspect the specific targets you want to be different and change the TARGET_SPECIFIC_ZERO_LINK setting to NO.
You can do this with optimization flags, warnings, versions, basically anything that you want to be generally consistent among targets but with some target-specific exceptions. Just use different custom build setting identifiers.
Chris |