From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-03-15 11:18:12
On Monday 14 March 2005 20:35, Joao Abecasis wrote:
> >>I had noticed this too... In order to have quickbook compiled only once
> >>quickbook is always compiled with the "default" toolset. In practice, we
> >>get an empty property-set:
> >> local quickbook-property-set = [ property-set.empty ] ;
> >>This is not the toolset specified on the command line but the first one
> >>ever defined. (<variant>release is also explicitly added which may not
> >>always be desirable...)
> I'm not sure how I can fix the above issue... The original motivation
> for choosing a single toolset was to avoid having multiple quickbook
> executables built for the sole purpose of generating docs.
> This design allows one to generate docs by specifying only the output
> format on the command-line:
> bjam --v2 pdf
> Quickbook, boostbook et al. are implementation details.
> There may be other ways to select the "default" toolset but, given my
> limited knowledge of Boost.Build, I'm at loss here.
I'm at loss why you're at loss. There are two alternatives:
1. You always build quickbook with the default toolset (which is the first
2. You build quickbook with whatever toolset user has specified on the command
line. Note that if a user has not specified any toolset on the command line,
everything will be built with the default one (again, the first declared).
If you want the first behaviour, you use
local quickbook-property-set = [ property-set.empty ] ;
If you want the second, you use the build properties passed to quickbook
> Maybe the question could be which toolset an empty property-set selects.
> Should a toolset explicitly stated on the command-line take precedence?
I don't see why. The tool specified on the command line is already in build
properties, if you don't want to build quickbook once, you can just use those
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