On 11/18/2013 11:05 PM, Steven Watanabe wrote:
AMDG
On 11/18/2013 07:48 PM, Edward Diener wrote:
There are 4 lines of C++FLAGS
toolset.flags msvc.compile C++FLAGS <exception-handling>on/<asynch-exceptions>off/<extern-c-nothrow>off : /EHs ; toolset.flags msvc.compile C++FLAGS <exception-handling>on/<asynch-exceptions>off/<extern-c-nothrow>on : /EHsc ; toolset.flags msvc.compile C++FLAGS <exception-handling>on/<asynch-exceptions>on/<extern-c-nothrow>off : /EHa ; toolset.flags msvc.compile C++FLAGS <exception-handling>on/<asynch-exceptions>on/<extern-c-nothrow>on : /EHac ;
How is a particular one chosen ?
Look at the properties. If you compile with async-exceptions=on extern-c-nothrow=on, you'll get /EHac, for instance. The default for both is "off"
Are "defaults" harcoded somewhere or are they in some .jam file ? In the original command line I showed: "tuple.cpp" -Fo"some_long_path\tuple.obj" -TP /Z7 /Od /Ob0 /W4 /GR /MDd /Zc:forScope /Zc:wchar_t /wd4675 /EHs -c I am not setting any of those options in my user-config.jam or site-config.jam. Yet they are being generated, and maybe they are "defaults" also, but they must be coming from somewhere.
In Christ, Steven Watanabe
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost