Edward Diener wrote:
Peter Dimov wrote:
'bjam' (or 'bjam --toolset=foo' if the default doesn't work)
This now gets into understanding how bjam works. Argh !!!
I don't see why. Peter just mentioned what you could find out by reading the Boost Library guidelines, and by running "bjam --help".
How does one find out the name of the toolset which corresponds to the compiler/version which one wants to test ?
The toolset names are documented in the getting started docs. And the version number is irrelevant.
I am assuming that one must look at Boost Build documentation to determine this.
No. Just reading the getting started docs <http://www.boost.org/more/getting_started/windows.html#identify-your-toolset>. Which you would do if you are a user.
However, let us say for VC++, the name msvc only specifies a compiler but not a version. Now one has to investigate how one specifies both a compiler and a version on the bjam command line.
No. The version is irrelevant. And in the case of some toolsets, like msvc, detected automatically. You don't need to specify the version if you are a user. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo