diff options
author | Tanner Gooding <tagoo@outlook.com> | 2017-03-07 18:04:25 -0800 |
---|---|---|
committer | Tanner Gooding <tagoo@outlook.com> | 2017-03-07 18:04:25 -0800 |
commit | d6158c82c37c72a9af96d5b51139a821b8071f1c (patch) | |
tree | b68ac151981d303d00b3fbf1c125aa7c0f5d531c /run.cmd | |
parent | 029c38fa726ccfc5bf3e18a567075643ee5efd35 (diff) | |
download | coreclr-d6158c82c37c72a9af96d5b51139a821b8071f1c.tar.gz coreclr-d6158c82c37c72a9af96d5b51139a821b8071f1c.tar.bz2 coreclr-d6158c82c37c72a9af96d5b51139a821b8071f1c.zip |
Updating the various windows build scripts to have a comment explaining the VS version selection logic.
Diffstat (limited to 'run.cmd')
-rw-r--r-- | run.cmd | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -1,6 +1,21 @@ @if not defined _echo @echo off setlocal +:: Default to highest Visual Studio version available +:: +:: For VS2015 (and prior), only a single instance is allowed to be installed on a box +:: and VS140COMNTOOLS is set as a global environment variable by the installer. This +:: allows users to locate where the instance of VS2015 is installed. +:: +:: For VS2017, multiple instances can be installed on the same box SxS and VS150COMNTOOLS +:: is no longer set as a global environment variable and is instead only set if the user +:: has launched the VS2017 Developer Command Prompt. +:: +:: Following this logic, we will default to the VS2017 toolset if VS150COMNTOOLS tools is +:: set, as this indicates the user is running from the VS2017 Developer Command Prompt and +:: is already configured to use that toolset. Otherwise, we will fallback to using the VS2015 +:: toolset if it is installed. Finally, we will fail the script if no supported VS instance +:: can be found. if not defined VisualStudioVersion ( if defined VS150COMNTOOLS ( if not exist "%VS150COMNTOOLS%\..\IDE\devenv.exe" goto NoVS |