Re: [jamboost] Re: BB4

From: David Abrahams (dave_at_[hidden])
Date: 2003-01-08 15:07:28

Vladimir Prus <ghost_at_[hidden]> writes:

> David Abrahams wrote:
>> 
>> 
>> It would help a bit if I could get the testing program to show me the
>> build commands it executes...
>
> We'd have to tweak TestCmd.py for that... around like 407...

I added a --verbose option to BoostBuild.py. Seems to work.
As a result I note that the last command-line has somewhat suspicious
repetition:

g++ -g -o bin\gcc\debug\main-target-e\e.exe bin\gcc\debug\main-target-e\e.o bin\gcc\debug\d.dll -Wl,-Bdynamic -Wl,-Bstatic bin\gcc\debug\d.dll -Wl,-Bdynamic -Wl,-Bstatic -Wl,-Bdynamic 

Added files : ['bin/gcc/debug/a.exe', 'bin/gcc/debug/a.o', 'bin/gcc/debug/b.exe', 'bin/gcc/debug/b.o', 'bin/gcc/debug/d.dll', 'bin/gcc/debug/x.cpp', 'bin/gcc/debug/x.h', 'bin/gcc/debug/x.o', 'bin/gcc/debug/y.cpp', 'bin/gcc/debug/y.h', 'bin/gcc/debug/y.o', 'bin/gcc/debug/main-target-c/c.exe', 'bin/gcc/debug/main-target-c/c.o', 'bin/gcc/debug/main-target-e/e.exe', 'bin/gcc/debug/main-target-e/e.o']
Removed files : []
Modified files: []
Touched files : []
File bin/gcc/debug/a.exe not touched as expected
c:\boost\tools\build\test\..\jam_src\bin.ntx86\bjam -sBOOST_BUILD_PATH=c:\boost\tools\build\test\..\new -d+2 
FAILED test of c:\boost\tools\build\test\..\jam_src\bin.ntx86\bjam -sBOOST_BUILD_PATH=c:\boost\tools\build\test\..\new -d+2 
at line 304 of BoostBuild.py (expect_touch)
from line 19 of dependency_test.py

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution