|
|
Boost Testing : |
From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2005-07-11 15:28:45
Beman Dawes writes:
> I've tracked down the problem that was preventing my tests from using a
> local jamfile in the runner directory.
>
> bjam is getting invoked with the command line:
>
> # Starting tests
> (F:\boost-auto-regr\boost\tools\build\jam_src\bin.ntx86\bjam.ex
> e
> "-sBOOST_BUILD_PATH=F:\boost-auto-regr:F:\boost-auto-regr\boost\tools/build/v1
> " "-sBOOST_ROOT=F:\boost-auto-regr\boost" "-sTOOLS=cw-9_4 gcc-3_3_3-cygwin
> intel
> -win32-8_1" -d2 --dump-tests
> "-sALL_LOCATE_TARGET=F:\boost-auto-regr\results" >
>>F:\boost-auto-regr\results\bjam.log 2>&1)...
>
> Notice the three colons in
> "-sBOOST_BUILD_PATH=F:\boost-auto-regr:F:\boost-auto-regr\boost\tools/build/v1"
That's the format David provided us with in
http://lists.boost.org/MailArchives/boost/msg75986.php. Dave?
[...]
> If that gets changed to:
>
> def bjam_command( toolsets ):
>
> # result = '%s "-sBOOST_BUILD_PATH=%s:%s" "-sBOOST_ROOT=%s"'\
> result = '%s "-sBOOST_BUILD_PATH=%s" "-sBOOST_ROOT=%s"'\
> % (
> tool_path( bjam )
> , regression_root
> # , os.path.join( boost_root, 'tools/build/v1' )
> , boost_root
> )
>
> if not toolsets is None:
> result += ' "-sTOOLS=%s"' % string.join( string.split( toolsets,
> ',' ), ' ' )
>
> return result
>
> then the .jam file is found and the problem goes away.
I'm not sure how that could work if your custom toolset just includes
the one in "tools/build/v1" -- unless the latter directory is somehow
deduced from $BOOST_ROOT.
> Hopefully this will give the MetaCommunications folks enough
> information to fix the problem permanently.
Thanks for looking into it!
-- Aleksey Gurtovoy MetaCommunications Engineering