Skip to content

Commit 3501e41

Browse files
TylerMSFTTylerMSFT
authored andcommitted
wording
1 parent 4f46efd commit 3501e41

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/porting/binary-compat-2015-2017.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ We've changed this behavior in Visual Studio 2015 and later versions. The runtim
1414

1515
There are three important restrictions on binary compatibility between the v140, v141, v142, and v143 toolsets and minor numbered version updates:
1616

17-
- Binaries created with different versions of the v140, v141, v142, and v143 toolsets can be combined. The key rule is that the linker should only work with inputs built by toolsets that are the same version (or earlier) as itself. This applies to apps, import libraries, and static libraries. In some cases, an import library for an [implicitly linked](../build/linking-an-executable-to-a-dll.md#implicit-linking) DLL built by a later version of the toolset can be linked using an earlier version--especially if the import library strictly uses `extern "C"` for the imports/exports. Here are some examples of what this all means:
17+
- Binaries created with different versions of the v140, v141, v142, and v143 toolsets can be combined. The key rule is that the linker should only work with inputs built by a toolset that is the same version (or earlier) as itself. This applies to apps, import libraries, and static libraries. In some cases, an import library for an [implicitly linked](../build/linking-an-executable-to-a-dll.md#implicit-linking) DLL built by a later version of the toolset can be linked using an earlier version--especially if the import library strictly uses `extern "C"` for the imports/exports. Here are some examples of what this all means:
1818
- An app compiled with a 2017 toolset (v141, versions 15.0 to 15.9) can be linked to a static library compiled with Visual Studio 2019 version 16.2 (v142), but the linking must be done using a version 16.2 or later toolset.
1919
- A version 16.2 library can be linked to a version 16.4 app, but only if you use the 16.4 or later toolset.
2020
- Apps and libraries built using VS 2015, 2017, or 2019 can be linked together, but the linking must be done using a version of the toolset that is as recent as, or more recent than, the most recent toolset used to build any of the binaries.

0 commit comments

Comments
 (0)