|
|
Boost Testing : |
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-06-27 10:02:56
Vladimir Prus wrote:
> Rene Rivera wrote:
>
>> Andreas Huber wrote:
>>> Bronek Kozicki wrote:
>>>> (the latter one not visible yet - still being tested). Both are using
>>>> stlport
>>>> 5.0.2 instead of standard C++ library bundled with the compiler
>>>> (Visual C++ or GCC). I will update toolsets names to make it visible
>>>> in next run.
>>> There seems to be something very odd with mingw/stlport. The linker
>>> complains as if it wouldn't find just about any std lib class:
>>>
>>> http://tinyurl.com/nh5em
>>>
>>> Since the other test runner on the same platform reports similar
>>> results, this hints at toolset issue?
>> Yes, it's a problem I introduced in trying to fix the STLport 5 support
>> in BBv2. The problem is that STLport5 by default only comes in
>> multi-thread versions. And it also guards against single-thread code
>> linking with multi-thread STLport. Unfortunately BBv2 can't deal with
>> the problem coherently at the moment. I'll get back to trying to find a
>> solution tomorrow.
>
> FWIW, I still don't know how V1 deals with this problem. Will it build
> everything in MT mode, or something else?
BBv1 would force all builds into multi-thread mode. Not exactly the
nicest solution :-( Currently I'm attempting to have the single-thread
user code link to the multi-thread STLport. We'll see how that goes.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo