From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-09-21 09:40:43
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 find a best match.
For example, when building with with <code><toolset>gcc</code>,
alternative 2, will be selected, and when building with
<code><toolset>msvc</code> alternative 3 will be selected. In all other
cases, the most generic alternative 1 will be built.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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