Re: [v2] not responding to toolset

From: David Abrahams (dave_at_[hidden])
Date: 2005-03-14 08:54:04

Joao Abecasis <jpabecasis_at_[hidden]> writes:

> David Abrahams wrote:
>> 
>> in tools/quickbook/doc I did:
>> 
>> bash -c "export ICU_PATH=/cygdrive/c/src/icu && bjam -a --v2 toolset=gcc pdf"
>> 
>> But it continued to try to use vc7.1 until I moved
>> 
>> using gcc ;
>> 
>> to the top of my site-config.jam
>
> 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...)

Certainly *something* is making Cygwin GCC churn forever when it
compiles quickbook. Maybe it's the optimizer? Usually that sort of
thing is not the optimizer, but instead due to too much debug info
generated by templates...

> FWIW, you can specify the quickbook executable to be used with:
>
> using quickbook : /path/to/quickbook ;
>
> Anyway, there's surely room for improvement and I'm open to
> suggestions.

Well, you can fix the issues we discussed above ;-)

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