[Python-Dev] Visual Studio 2008 compiler option EHsc ? (original) (raw)
Jim Kleckner jek-gmane at kleckner.net
Fri May 16 01:44:38 CEST 2008
- Previous message: [Python-Dev] rename of ConfigParser module?
- Next message: [Python-Dev] Visual Studio 2008 compiler option EHsc ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In building a package with several platforms, I ran across the warning message below from Visual Studio 2008. Should we add the /EHsc option to the compile_options in distutils for MSVC? Or is it more complex than that...
This link describes the warning: http://tinyurl.com/4fmjue http://msdn.microsoft.com/en-us/library/2axwkyt4.aspx
This link describes a patch: http://tinyurl.com/63bqo2
http://projects.scipy.org/pipermail/numpy-discussion/2007-January/025527.html
=== Warning message:
C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\xstring(2092) : warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc
C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\xstring(2083) : while compiling class template member function 'void std::basic_string<_Elem,_Traits,_Ax>::_Copy(unsigned int,unsigned int)' with [ _Elem=char, _Traits=std::char_traits, _Ax=std::allocator ] C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\xstring(2221) : see reference to class template instantiation 'std::basic_string<_Elem,_Traits,_Ax>' being compiled with [ _Elem=char, _Traits=std::char_traits, _Ax=std::allocator ]
- Previous message: [Python-Dev] rename of ConfigParser module?
- Next message: [Python-Dev] Visual Studio 2008 compiler option EHsc ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]