|
|
Boost Testing : |
Subject: Re: [Boost-testing] statechart test Boost.Build failures on 1.38.0
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2009-03-06 00:44:39
Andreas Huber wrote:
> Hi Steve
>
>> I shortened the statechart tests down to this:
>> test-suite statechart
>> :
>> [ statechart-st-lib-run DllTestNormal
>> : TuTestMain : TuTest : <link>shared $(normal) ]
>> ;
>>
>> And I run the following command:
>> cd status &&
>> bjam -d2 --dump-tests --user-config=/Code/boost_1_38_0/user-config.jam --without-python
>> --without-thread --without-mpi variant=release threading=single
>> link=static runtime-link=static
>
> This test tries to establish how static objects defined in .hpp files are
> handled when a dll is involved. So the test only makes sense when at least
> some binaries are dynamically linked. Maybe the build fails because you try
> to force an all static build with the last two options, but I don't know
> enough about Boost.Build to say for sure.
Essentially, that's it. Some of the tests are DLLs. The above requests static linking.
DLLs with static linking are impossible on Linux. Whilst the diagnostic could be better,
I am not sure there's any way Boost.Build can respect this request.
- Volodya