Re: [BBv2 docs editorial] tutorial/conditions

From: David Abrahams (dave_at_[hidden])
Date: 2005-09-21 10:40:47

Vladimir Prus <ghost_at_[hidden]> writes:

> On Tuesday 20 September 2005 23:46, David Abrahams wrote:
>
>> > lib demangler : dummy_demangler.cpp ; # alternative
>> > 1 lib demangler : demangler_gcc.cpp : <toolset>gcc ; # alternative 2
>> > lib demangler : demangler_msvc.cpp : <toolset>msvc ; # alternative 3
>> >
>> > In the example above, when built with gcc or msvc, demangler will use
>> > a source file specific to the toolset. Otherwise, it will use a
>> > generic source file, dummy_demangler.cpp.
>>
>> Does it select the best match, or what? The reader needs to get at
>> least a very rough sense of how the alternative selection process
>> works at this point.
>
> I've modified this to be:
>
> When building <filename>demangler</filename>, Boost.Build will
> compare requirements for each alternative with build properties to
^--"the" ^--"the requested"

Does the reader know what "build properties" means at this point?

> find a best match. For example, when building with with
> <code>&lt;toolset&gt;gcc</code>, alternative 2, will be selected,
^---strike that

> and when building with <code>&lt;toolset&gt;msvc</code> alternative
either use a comma here or remove the one after "gcc"---^

> 3 will be selected. In all other cases, the most generic alternative
> 1 will be built.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com