Visual-C++-2017 二进制文件是否与 VC++-2015 兼容? [英] Is Visual-C++-2017 binary compatible with VC++-2015?

问题描述

Steve 告诉我 VC 2015 和 VC 2017 实际上(将)二进制兼容.

Steve tells me that VC 2015 and VC 2017 are actually (gonna be) binary compatible.

我发现 零 信息 wrt.这在 2017 (RC) 发行说明 - 或漂亮在任何地方都可以，所以这里是:

I found zero info wrt. this in the release notes for 2017 (RC) - or pretty much anywhere for that matter, so here goes:

• 是用VC++-2017 二进制兼容 VC++-2015 构建的 DLL?
• 2017 年和 2015 年是否使用相同(动态)运行时库?
• 如果是，那么平台工具集 Visual Studio 2017 (v141) 和 Visual Studio 2015 (v140) 之间的运行时 区别是什么?代码>?(*)

• Is a C++ (C++ interface) DLL built with VC++-2017 binary compatible with a DLL built by VC++-2015?
• Do 2017 and 2015 use the same (dynamic) runtime library?
• If so, what, if any, is the runtime difference between Platform Toolset Visual Studio 2017 (v141) and Visual Studio 2015 (v140)? (*)

(*):是的，我其实是安装了2017的RC，从表面上看，至少使用了相同的MSVCRT，也就是msvcp140.dll 和 vcruntime140.dll(尽管平台工具集被称为v141".

(*): Yeah, I actually went ahead and installed the 2017 RC, and from what I can see on the surface, at least the identical MSVCRT is used, that is msvcp140.dll and vcruntime140.dll (despite the platform toolset being called "v141".

推荐答案

是的，141 和 140 库几乎相同.该版本因并行问题而受到冲击.VisualC++ 2015 中的 v140 工具集和 VC++ 2017 中的 v141 工具集是二进制兼容的.

Yes, the 141 and 140 libraries are almost identical. The version was bumped for a side-by-side issue. The v140 toolset in VisualC++ 2015 and v141 toolset in VC++ 2017 are binary compatible.

这篇关于Visual-C++-2017 二进制文件是否与 VC++-2015 兼容?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！