Re: [v2] not responding to toolset

From: David Abrahams (dave_at_[hidden])
Date: 2005-03-22 10:38:56

Vladimir Prus <ghost_at_[hidden]> writes:

>>
>> My decision was not tied to quickbook knowledge. I also think the
>> default toolset is a good idea. I just think it seems natural to
>> override the "default" from the command line.
>
> Maybe we have different ideas of "default". What I mean is that I have an 
> extra cool tool which takes image file and converts it into a C++ file (just 
> an example), I want to build it with gcc/debug, and don't want it to be 
> rebuilt when I type
>
> bjam gcc-4.0
>

It seems obvious to me that there should be a way to explicitly
request a build **and install** of a tool like quickbook. E.g.:

bjam gcc debug quickbook

Once installed, rules that try to use quickbook would pick up the
installed tool and not try to build a new one with any compiler
specified on the command-line. If there was no installed quickbook,
they'd just build their own copy of the tool as required. I think
this can easily be accomplished with bjam's builtin SEARCH and LOCATE
features; if it can't we should fix that. I'm not sure how amenable
the structure of BBv2 itself is, however.

Maybe it would be a good to be able to explicitly disable use of the
installed tool also, but that's less important.

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