Re: [boost] [test] Re: Conflicts when building libraries at root

Vladimir Prus writes:

So why is Boost.Test enabling those? Are there any particular files in Boost.Test that need it? If so, we can change Jamfile to only compile those files with asynch exceptions, without propagating it to dependencies.

I am sure execution_monitor.cpp needs it. Frankly I do not remember for sure at this point, but I thought all the components of the test module will need to be built with /EHa for Boost.Test to be able to catch SEH successfully. What is the problem we are trying to solve?