Re: Yet another build styles question
Re: Yet another build styles question
- Subject: Re: Yet another build styles question
- From: Scott Tooker <email@hidden>
- Date: Tue, 28 Oct 2003 16:06:23 -0800
The short answer is that $(value) is the new replacement for the +=
behavior. It's more powerful than += since you can indicate where the
value of the underlying build setting goes (with +=, the value you
provided for the build setting was always appended to the end of the
pre-existing build setting).
So a little review here, Xcode (like Project Builder) has a series of
"layers" for determining what get's overriden.
Command Line
Build Style
Target
Built-in Defaults
(There are more layers, but the ones above cover the common cases).
Layers that are higher in the stack override lower layers. So setting a
build setting in a build style overrides the value set in the target.
So if I have a build setting for "Header Search Paths" in the active
target defined as "foo/bar" and the active build style defines "Header
Search Paths" to be "/baz/bogos $(value) /fubar/grok", then the actual
value for the build setting given this is "/baz/bogos foo/bar
/fubar/grok".
Note that there is a difference between the definition for a build
setting at any given level, versus the actual value once all the layers
take affect (in practice the vast majority of the time you have three
cases, the definition at the target layer is not modified by higher
layers, the build style defines a new build setting not present in the
lower layers, or the build style modifies/replaces a definition from
the lower layers).
Scott
On Oct 28, 2003, at 12:26 PM, Bill Cheeseman wrote:
> on 03-10-28 2:03 PM, Scott Tooker at email@hidden wrote:
>
>> Header Search Paths = /my/new/path/here $(value) /my/other/path/here
>
> Pardon my denseness.
>
> Does this give you whatever was in Header Search Paths in some
> inherited
> context (e.g., target build settings), plus /my/new/path/here and
> /my/other/path/here in the current context (e.g., a build style)? But
> isn't
> the build style always supposed to inherit from the target build
> setting,
> anyway? If not, then I have misunderstood the whole idea and many of my
> Xcode build styles are wrong because they are overriding rather than
> accumulating the target build settings (this could explain a lot of the
> problems I've been having).
>
> In other words, should the $(value) construct be very commonly used --
> that
> is, everywhere that you would have used += in Project Builder?
>
> I must say that the documentation for all this in the Xcode (and the
> old
> Project Builder) release notes is less than clear to somebody who isn't
> already well versed in the subject.
>
> --
>
> Bill Cheeseman - email@hidden
> Quechee Software, Quechee, Vermont, USA
> http://www.quecheesoftware.com
>
> The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
> Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes
> _______________________________________________
> 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.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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.