Ross Ridge wrote: > MSVCRT.DLL has been a standard system compent of Windows since at least > Windows 98. Many other system components depend on it. Essentially, > MSVCRT.DLL is an "undocumented" part of the Windows API. It's not > exactly "endorsed", Microsoft would rather you use it's current > compiler and runtime, but it is the standard "official" Windows system > C library.
See http://msdn2.microsoft.com/en-us/library/abx4dbyh(VS.80).aspx 'The msvcrt.dll is now a "known DLL," meaning that it is a system component owned and built by Windows. It is intended for future use only by system-level components.' The SDK stopped including an import library for it (I believe earlier versions of the SDK still had an import library). Regardless, there is no version of the MS C++ library that links against msvcrt.dll. So if Python is linked against msvcrt.dll, you can't really build C++ extensions anymore (with MSVC), unless you are certain that mixing CRTs causes no harm for your application. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
