Re: [Boost-build] Broken V2 testing.

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-10-24 10:27:35

Vladimir Prus wrote:
> Rene, as I've said in an email some time ago you need to use
> 
>    python test_all.py gcc-mingw_specific-3.4.5 

I don't remember you saying that :-(

> I think it's not very hard to specify by hand,

It is when the toolset condition is being autodetected.

> and on the other hand it's
> pretty hard to make the Python-based test system figure out which toolset
> is defined first in your user-config.jam.

Except that the above is not the first toolset in my user-config:

====
import toolset : using ;

path-constant DEVELOPMENT : C:/Development ;

using msvc : all ;

using gcc : : C:/MinGW/bin/g++.exe ;
====

So it's some toolset the test program decides it should use. As making 
the test system figure out the toolset we can easily support a 
"--show-tools" option and have the test system read in the result.

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