Bronek Kozicki writes:
Aleksey Gurtovoy wrote:
* I'd like to test MINGW 3.4.1 (release candidate) with Boost. Should I use toolset MINGW?
Preferably "mingw-3.4.1" (again, just checked in).
Hm. Something is wrong :
# Getting sources (Mon, 02 Aug 2004 06:28:52 +0000)... # Downloading 'C:\MinGW341\Bronek\boost\boost.tar.bz2' for tag CVS-HEAD from www.boost-consulting.com... # Looking for old unpacked archives... # Unpacking boost tarball ("C:\MinGW341\Bronek\boost\boost.tar.bz2")... # Unpacked into directory "C:\MinGW341\Bronek\boost\boost-04-08-01-2300"
C:\MinGW341\Bronek\boost\boost\tools\build\jam_src>build.bat mingw-3.4.1 ### ### "Unknown toolset: mingw-3.4.1" ### ### You can specify the toolset as the argument, i.e.: ### .\build.bat msvc ### ### Toolsets supported by this script are: borland, como, gcc, gcc-nocygwin, intel-win32, metrowerks, mingw, msvc, vc7 ###
Oh, sorry, I should have mentioned that due to recent changes, if you don't have prebuilt bjam executable in the 'regression.py' directory, and you are using a numbered toolset, then you need to specify the bjam bootstrap toolset separately (since it only supports a few), using the '--bjam-toolset' option: python regression.py --runner=<your runner id> --toolsets=mingw-3.4.1 --bjam-toolset=vc7 I guess we could determine this situation and fall back to the default bjam toolset automatically. We'll look into this. -- Aleksey Gurtovoy MetaCommunications Engineering