Re: [Boost-build] build documentation flaws

Subject: Re: [Boost-build] build documentation flaws
From: Daniel Krügler (dsp_at_[hidden])
Date: 2008-11-05 04:03:42

Jürgen Hunold wrote:
> Hi Daniel !
> 
> An'n Mittwoch 05 November 2008 hett Daniel Krügler schreven:
>> Finally, I would like to ask a question: If I correctly understand the
>> bjam help, I can invoke bjam with the command line
>>
>> bjam root="C:\Program Files\Some_Dir" --toolset=X ..
> 
> *sigh*, that should be "toolset=X". Please omit the "--" before toolset.

This surprises me, because

http://www.boost.org/doc/libs/1_37_0/more/getting_started/windows.html#invoke-bjam

gives this example of a bjam invokation:

bjam --build-dir=build-directory --toolset=toolset-name 
--build-type=complete stage

Mind to explain?

>> to specify the root directory of the compiler installation for a large
>> set of compilers - interestingly *not* for all of them. I wonder why
>> e.g. HP aC++, Borland C++, or Digital Mars C/C++ do not provide this
>> functionality? (I tend to prefer to provide such information as a
>> command line parameter instead of manipulating a bjam file).
> 
> This works only for toolsets with autodetection. That would be gcc and msvc.
> I think that all other toolsets have to be configured in user-config.jam or 
> site-config.jam.
> 
> Then specifing "toolset=whateveryounameit" should work.

OK, thanks. Obviously I misunderstood

http://www.boost.org/doc/libs/1_37_0/doc/html/jam/building.html

table 29.1, which says "The supported toolsets, and wether they are 
auto-detected[..]:"

The table contains e.g. darwin and I miss the definition of
auto-detection. Maybe something like: Where "Common install locations"
is defined?

- Daniel