Re: [v2] not responding to toolset

From: Joao Abecasis (jpabecasis_at_[hidden])
Date: 2005-03-22 07:29:50

Vladimir Prus wrote:
>>What I would like to happen here would be for the quickbook executable
>>to be built once with a "default" toolset (from the above command-line
>>I'd expect it to be gcc-release). 
> 
> 
> The only way to accomplish that is make the quickbook generator remember if it 
> was already invoked. It it was, it can return the same targets as it returned 
> the last time.

Hmmm... This could be done for quickbook, I guess. But it still wouldn't 
solve the problem on boostbook's side.

>>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

Right! I can see both options as valid user expectations. Is there a way 
to override the default toolset from the command line? Perhaps something 
like:

bjam default=gcc-4.0

This should cater to both needs. The user would choose with care the 
default toolset because it has "special privileges". But s/he could 
still override it from the command-line.

I guess this capability is more important for the tool-developers, than 
for the end users.

Anyway, if a common policy is agreed on for Boost.Build, I'll happilly 
change quickbook to follow suit.

>>Btw, how can I define a default toolset and mode (release/debug) other
>>than changing the order in which toolsets are declared?
> 
> 
> bjam --help feature.set-default
> 
> It's a bit risky to use it anywhere but in user-config.jam, though, because 
> what if two Jamfiles try to set it to different values?

Thanks! I wanted this for user-config.

Regards,

João