|
Boost Testing : |
From: Misha Bergal (mbergal_at_[hidden])
Date: 2006-12-02 20:02:10
JoaquÃn M López Munoz wrote:
> Aleksey Gurtovoy <agurtovoy <at> meta-comm.com> writes:
>
[...]
>> Unfortunately, we don't automatically archive bjam log from the
>> previous run, so we have to wait for the current one to finish to
>> take a deeper look at what's happening here.
>
> Hello again, excuse my being such a pest, new results showed
> up today and the CW column is still empty --with the curious
> exception of program_options, half of whose cells exhibit
> results. Maybe you can have a look at this?
>
The problem seems to be in the build system itself - it just
does not build and run most (practically all) tests. I am not
qualified to figure out what is wrong, but I've collected some
info which might help a more knowledgeable person to track this down:
1. bjam.log produced by
"D:\Users\lesha\trunk.scripts_boost_regression\boost\tools\jam\src\bin.ntx86\bjam.exe"
--v2
"-sBOOST_BUILD_PATH=D:\Users\lesha\trunk.scripts_boost_regression"
"-sBOOST_ROOT=D:\Users\lesha\trunk.scripts_boost_regression\boost"
cw-8.3/runtime-link=static
-d2 --dump-tests -d5
"--build-dir=D:\Users\lesha\trunk.scripts_boost_regression\results"
1>>"D:\Users\lesha\trunk.scripts_boost_regression\results\bjam.log" 2>&1
is located at http://engineering.meta-comm.com/resources/cw-8.3-problem/bjam.zip
2. The following modification to lib/filesystem/test/Jamfile.v2 seems to make
path_test.cpp running (obviously this is not a way to fix it, but a piece of info
which might help)
--- Jamfile.v2 7 Nov 2006 12:56:06 -0000 1.3.2.1
+++ Jamfile.v2 3 Dec 2006 00:45:45 -0000
@@ -9,7 +9,7 @@
project
: requirements <library>/boost/filesystem//boost_filesystem
- <define>BOOST_ALL_NO_LIB
+ <define>BOOST_ALL_NO_LIB <link>static
;
test-suite "filesystem" :
@@ -17,8 +17,8 @@
: : : <define>BOOST_FILESYSTEM_STATIC_LINK
<runtime-link>static <link>static
]
- [ run path_test.cpp
- : : : <define>BOOST_FILESYSTEM_DYN_LINK
+ [ run path_test.cpp
+ : : : <link>shared <define>BOOST_FILESYSTEM_DYN_LINK=1
: path_test_dll
]
[ run operations_test.cpp
Again, somebody knowledgeable needs to look at it, I am afraid I
don't have a clue how this supposed to work :(.
-- Misha Bergal MetaCommunications Engineering