[Boost-build] build documentation flaws

Subject: [Boost-build] build documentation flaws
From: Daniel Krügler (dsp_at_[hidden])
Date: 2008-11-05 02:43:07

Hi,

there are two points which I think should be clarified or fixed in
the documentation of the build process described in

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

1) The text says:

"Building the special stage target places Boost library binaries in the 
stage\ subdirectory of your build directory 
[http://www.boost.org/doc/libs/1_37_0/more/getting_started/windows.html#build-directory]."

This is not what I observe. If I define

--build-dir=X

to some value X this X is ignored concerning the stage.
The boost build *always* creates a stage directory as a child of the 
directory where the corresponding Jamroot is located.
I guess, the missing information is, that --stagedir allows redirection 
of the stage location.

2) I suggest to add to

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

the information that --buildid=xy (if provided) causes that "-xy" is 
attached just after the version tag.

to complete the documentation which explains the library naming.

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

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

Greetings from Bremen,

Daniel