From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-10 04:52:19
Rene Rivera wrote:
> Vladimir Prus wrote:
>> Then it's probably some Windows-specific issue with search paths. For a
>> start, can you create test/test-config.jam and add
>> using gcc ;
>> there? If that works out, and there are no further issues, we can
>> investigate why your user-config.jam is not found.
> With a partial test-config.jam (I copied the user-config and commented
> out stuff until it worked) I get farther...
> === test-config.jam
> import toolset : using ;
> using msvc : all ;
> using gcc : 3.4.5 : C:/MinGW/bin/g++.exe ;
> grafik_at_KLUDGE /c/DevRoots/Boost/boost/tools/build/v2/test
> $ python generators_test.py
> File bin/gcc/debug/a.o not added as expected
> -------- all changes caused by last build command ----------
> Added files : ['lib/bin/gcc-3.4.5/debug/c.o',
> 'lib/bin/gcc-3.4.5/debug/libauxilliary.a', 'bin/gcc-3.4.5/debug/a.exe',
> 'bin/gcc-3.4.5/debug/a.o', 'bin/gcc-3.4.5/debug/b.o',
Please run tests as:
python test_all.py gcc-3.4.5
so that test system knows that name of toolset to expect.
> -sBOOST_BUILD_PATH=c:\DevRoots\Boost\boost\tools\build\v2\test -d0 --quiet
> at line 391 of
> c:\DevRoots\Boost\boost\tools\build\v2\test\BoostBuild.py (fail_test)
> from line 405 of
> from line 11 of generators_test.py
> in directory: c:\docume~1\grafik\locals~1\temp\tmpivbv8-
> Is there a way to have it *not* use the bjam versions built inside the
> boost tree (jam/src/bin*/bjam)? Frequently I'm working on those builds,
> and hence are neither up to date nor stable. I'd rather that it used the
> bjam in my path.
The idea is that tests should test working dir state, so that if you break
bjam you know about it. If you independently work on some Boost.Build
changes and Boost.Jam changes and don't want test results to fix up, I
think it's possible to make two separate checkouts of the 'v2' directory.
Would that work for you?
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