changeset 13200:017a81187128 v8.0.1474

patch 8.0.1474: Visual C 2017 has multiple MSVCVER numbers commit https://github.com/vim/vim/commit/dd08b6a32b639b8c7a11275e04ae0a7ffc43aed0 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Feb 6 22:02:43 2018 +0100 patch 8.0.1474: Visual C 2017 has multiple MSVCVER numbers Problem: Visual C 2017 has multiple MSVCVER numbers. Solution: Assume the 2017 version if MSVCVER >= 1910. (Leonardo Valeri Manera, closes #2619)
author Christian Brabandt <cb@256bit.org>
date Tue, 06 Feb 2018 22:15:05 +0100
parents 342b4166d135
children e57e06cfb76b
files src/Make_mvc.mak src/version.c
diffstat 2 files changed, 4 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/src/Make_mvc.mak
+++ b/src/Make_mvc.mak
@@ -289,7 +289,8 @@ MSVC_MAJOR = ($(MSVCVER) / 100 - 6)
 MSVCRT_VER = ($(MSVCVER) / 10 - 60)
 # Visual C++ 2017 needs special handling
 # it has an _MSC_VER of 1910->14.1, but is actually v15 with runtime v140
-!elseif $(MSVCVER) == 1910
+# TODO: what's the maximum value?
+!elseif $(MSVCVER) >= 1910
 MSVC_MAJOR = 15
 MSVCRT_VER = 140
 !else
--- a/src/version.c
+++ b/src/version.c
@@ -772,6 +772,8 @@ static char *(features[]) =
 static int included_patches[] =
 {   /* Add new patch number below this line */
 /**/
+    1474,
+/**/
     1473,
 /**/
     1472,