From c61131380da73221a6590f7898d68b35a8450891 Mon Sep 17 00:00:00 2001 From: stijn Date: Mon, 20 Mar 2017 16:15:46 +0100 Subject: [PATCH] windows: Make msvc project file support any version from VS2013 to VS2017 Instead of having the PlatformToolset property hardcoded to a specific version just set it to the value of DefaultPlatformToolset: this gets defined according to the commandline environment in which the build was started. Instead of just supporting VS2015 the project can now be built by any version from VS2013 to VS2017 and normally future versions as well, without quirks like VS asking whether you want to upgrade the project to the latest version (as was the case when opening the project in VS2017) or not being able to build at all (as was the case when opening the project in VS2013). Also adjust the .gitignore file to ignore any artefacts from VS2017. --- windows/.gitignore | 1 + windows/micropython.vcxproj | 8 ++++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/windows/.gitignore b/windows/.gitignore index ec28212111..12235e7c9e 100644 --- a/windows/.gitignore +++ b/windows/.gitignore @@ -7,4 +7,5 @@ *.ilk *.filters /build/* +.vs/* *.VC.*db diff --git a/windows/micropython.vcxproj b/windows/micropython.vcxproj index 6f6e11ab4a..ee0b98abba 100644 --- a/windows/micropython.vcxproj +++ b/windows/micropython.vcxproj @@ -26,26 +26,26 @@ Application true - v140 + $(DefaultPlatformToolset) MultiByte Application false - v140 + $(DefaultPlatformToolset) true MultiByte Application true - v140 + $(DefaultPlatformToolset) MultiByte Application false - v140 + $(DefaultPlatformToolset) true MultiByte