|
|
Boost Testing : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2007-10-08 08:30:24
Nicola Musatti wrote:
> Hartmut Kaiser wrote:
>> Nicola,
>>
>>>> Hm, looking further I would guess it's because of using the same
>>>> sources for both the testwave and testwave_dll tests. Which
>>> is causing
>>>> a build collision. Unlike BBv1, BBv2 puts all the targets
>>> for sources
>>>> at the same "level" in a project. So I'm seeing the best
>>> way to work around this.
>>>
>>> As far as I know both Spirit and Serialization do the same
>>> thing extensively. Maybe there's something from their
>>> approach that may be applied to Wave?
>> AFAIU, none of these libraries use the same test file for different test
>> cases (I verified this). Do I miss something here?
>
> As far as I can tell Serialization does run each test both in static and
> dynamic link configuration on each test source file under
> libs/serialization/test .
Both System and Filesystem libraries run several of their tests as both
static and shared. The Boost.System Jamfile.v2 is below.
--Beman
---------------
project
: requirements
<library>/boost/system//boost_system
<define>BOOST_ALL_NO_LIB
<toolset>msvc:<asynch-exceptions>on
;
test-suite "system"
: [ run error_code_test.cpp
: # command line
: # input files
: # requirements
<define>BOOST_SYSTEM_STATIC_LINK
<link>static
]
[ run error_code_test.cpp
: : : <define>BOOST_SYSTEM_DYN_LINK
: error_code_test_dll
]
[ run error_code_user_test.cpp
: : : <define>BOOST_SYSTEM_STATIC_LINK
<link>static
]
[ run error_code_user_test.cpp
: : : <define>BOOST_SYSTEM_DYN_LINK
: error_code_user_test_dll
]
[ run system_error_test.cpp
: : : <define>BOOST_SYSTEM_STATIC_LINK
<link>static
]
[ run system_error_test.cpp
: : : <define>BOOST_SYSTEM_DYN_LINK
: system_error_test_dll
]
[ run initialization_test.cpp
: : : <define>BOOST_SYSTEM_DYN_LINK
]
[ run header_only_test.cpp
: : : <link>static
]
;