From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-09-12 02:43:23
David Abrahams wrote:
> From: "Vladimir Prus" <ghost_at_[hidden]>
>>In the meanwhile, can you take a look at the change to
>>boost_build_v2.html I recently comitted? It hopefully closes all the
>>issues you've raised so far.
> OK. I'll also make some edits for English usage.
Good. Guess you'll just commit those edits -- when it comes to your
comment on English, I can only nod ;-)
>>I can also offer a couple of tasks for you, if you like.
>>First is to document build variants in the docs, somewhere together with
> AFAICT features are already documented, so you must mean that you'd like
> 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 two
> 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. 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.
>>Also, it would be
>>great if you could document build request and its expansion.
> Ah, yes. OK, I'll try.
>>Second can probably help you to learn new code. It's currently not
>>possible to specify targets in command line. I guess it would be simple
>>to allow it, by tweaking build-system.jam. Guess it should try, for
>>each target, to locate it using "project.find-target" and set up
>>appropriate dependencies. Are you interested in trying?
> OK, I'll give that a shot.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk