From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-24 13:39:46
On Tuesday 24 October 2006 18:27, Rene Rivera wrote:
> 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.
No, it looks it's the auto-detected version of 'gcc' ;-)
> 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.
Perphaps, I'm not sure how that will mix with that auto-detection of gcc
version -- we need to have the auto-detected version printed.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk