Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#951 closed defect (fixed)

setenvironment.bat: Support VS2017 (with 2015 compiler workload)

Reported by: jng Owned by: jng
Priority: major Milestone: 4.1.0
Component: Build System Version: 4.1.0
Severity: 3 Keywords:
Cc: External ID:

Description

The current setenvironment.bat does not properly set up the build environment if the installation is VS2017 with the 2015 compiler workload enabled.

According to this (https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes-v15.3#C++ToolsetLibs15), for such installations, we should test for and call vcvarsall.bat in $VSINSTALL\2017\$EDITION\VC\Auxiliary\Build with -vcvars_ver=14.0

setenvironment.bat should check for these paths first and call vcvarsall.bat with the -vcvars_ver=14.0 argument if required.

Change History (2)

comment:1 Changed 4 years ago by jng

Resolution: fixed
Status: assignedclosed

In 7652:

For VS2017 (with MSVC 2015 compiler workload) the current setenvironment.bat does not properly set up the build environment.

This updates setenvironment.bat to test for VS2017 paths first and if present, call its vcvarsall.bat with the -vcvars_ver=14.0 argument to instruct it to use the Visual C++ 2015 (v140) toolset.

Fixes #951

comment:2 Changed 4 years ago by jng

In 7653:

Merged revision(s) 7652 from trunk:
For VS2017 (with MSVC 2015 compiler workload) the current setenvironment.bat does not properly set up the build environment.

This updates setenvironment.bat to test for VS2017 paths first and if present, call its vcvarsall.bat with the -vcvars_ver=14.0 argument to instruct it to use the Visual C++ 2015 (v140) toolset.

Fixes #951
........

Note: See TracTickets for help on using tickets.