From 6346ffeacaf57b7ecf1fac700490a0250a65e4ca Mon Sep 17 00:00:00 2001 From: Christian Kandeler Date: Thu, 4 Oct 2018 14:30:20 +0200 Subject: MSVC: Add support for the Visual Studio 2017 Build Tools This entails: - Auto-detection: The Build Tools no longer have an entry in the registry; use the vswhere tool instead. - Unset the VSINSTALLDIR environment variable before calling the vcvarsall.bat script, as this variable can confuse the msbuild.bat sub- script if it is set. - Look for the base include directory two levels above the directory under which cl.exe is located. Change-Id: Id8f7976e5f41015e59850d3ed68fa81b6ce701a2 Reviewed-by: Alexandru Croitor --- changelogs/changes-1.12.2.md | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 changelogs/changes-1.12.2.md (limited to 'changelogs') diff --git a/changelogs/changes-1.12.2.md b/changelogs/changes-1.12.2.md new file mode 100644 index 000000000..f578c8357 --- /dev/null +++ b/changelogs/changes-1.12.2.md @@ -0,0 +1,2 @@ +# Important bugfixes +* The Visual Studio 2017 Build Tools are properly supported now. -- cgit v1.2.3