From: Joao Abecasis (jpabecasis_at_[hidden])
Date: 2005-03-15 15:01:40
Vladimir Prus wrote:
>>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
> declared one)
I used to sympathize with this option because it gave the toolset more
control, like setting <variant>release by default. However, it seems
that this approach doesn't live up to the user's expectations.
> 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).
I was trying to avoid generating quickbook multiple times if multiple
toolsets were provided on the command line... but now I see boostbook
itself already generates lots of errors in this scenario, so I can just
forget about it.
> 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
... patience ...
... deleting some lines from the quickbook toolset ...
Done! More power to the user!
Thanks for your input.
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