|
Boost : |
Subject: Re: [boost] [test] Re: Conflicts when building libraries at root
From: Jürgen Hunold (jhunold_at_[hidden])
Date: 2015-03-09 17:03:10
Hi Volodya,
Am Montag, 9. März 2015, 13:14:48 schrieb Vladimir Prus:
> I see, thanks. Naturally Boost.Test problem does not happen to me on Linux,
> for lacks of asynch-exceptions there.
Yes, the same here, unfortunately. And the current regression tests just don't
catch this because they don't run the plain "end-user" library builds.
> Who of Boost.Test maintainer(s) can explain why this feature is used, and
> dependency on boost.system?
The dependency chain is Boost.Test-> Boost.Timer -> Boost.Chrono ->
Boost.System. This propagates "asynch-exceptions" to Boost.System and causes
the clash.
I've tried to solve this by using the "header-only" variant of Boost.System,
but this was only half-hearted and reverted after some hazardous test runs :-(
> This does not seem like a feature we can globally set?
Perhaps we can, but I'm not an expert in vc exception handling...
Yours,
Jürgen
-- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold_at_gmx.eu ! Germany
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk