Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2002-09-12 16:29:48

From: "Vladimir Prus" <ghost_at_[hidden]>

> > AFAICT features are already documented, so you must mean that you'd
> > build variants documentation to appear nearby.
> > Boost.Build v1 already said this about build variants, which seems to
me to
> > be adequate:
> >
> > "A build variant, or simply variant is a named set of build properties
> > describing how targets should be built. Typically you'll want at least
> > separate variants: one for debugging, and one for your release code."
> >
> > Do you think more than that needs to be added?
> Yea, we'd need to mention that it's a composite feature and describe how
> they are declared, in pacticular that default values of non-optional
> features are incorporated into build variant automagically.

As it turns out, they are not. They are incorporated into the build
specification (expanded build request combined with target requirements)
automagically, but that's different... and the difference hinges on your
next point:

> Also, do we
> wan't some variant inheritance/extension/templates. I don't remember how
> it works in V1, so can't document this for V2.

Yes, we do. And if the base build variant doesn't specify the value of a
property that should not prevent a derived variant from specifying it.

David Abrahams * Boost Consulting
dave_at_[hidden] *


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at