I then went on to use dumpbin (can be ran from the VS Developer Command Prompt which you can launch from C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\LaunchDevCmd.bat ): dumpbin testDumpbinLib.lib /rawdata:1 > dumpbin.
Which is what I expected since I am running toolset 14.14 (see also ) When I compile this code in debug mode (turned off Precompiled headers in properties – C/C++), I get: 1>_MSC_VER (compiler verion) 1914 To find out what's new in Visual Studio 2015 Update 3, see the Visual Studio 2015 Update 3 Release Notes. Microsoft Visual C++ 2015 Redistributable includes bug fixes to the runtime DLLs and also the latest versions for KB 2999226. I added some preprocessor lines that print the _MSC_VER macro. These packages also install run-time components of C Runtime (CRT), Standard C++, MFC, C++ AMP, and OpenMP libraries. #pragma message( "_MSC_VER (compiler verion) " STRING(_MSC_VER)) To illustrate my problem, I created a static library testDumpbin.lib containing a simple class, testClass: I noticed that when I run dumpbin on a static library, I get a different version for _MSC_VER than expected. I am developing C++ in Visual Studio 2017, version 15.7, VCToolsVersion 8.
0 kommentar(er)
