From 191aa3022207df91cd2d057e1f90573b6b5809b8 Mon Sep 17 00:00:00 2001 From: Danny Scott Date: Fri, 27 Sep 2019 11:42:06 -0300 Subject: [PATCH] Update "MSVC binaries" section of the release build instructions Reflect currently used versions. Closes https://github.com/wxWidgets/wxWidgets/pull/1569 --- docs/contributing/how-to-release.md | 33 ++++++++++++++++++++--------- 1 file changed, 23 insertions(+), 10 deletions(-) diff --git a/docs/contributing/how-to-release.md b/docs/contributing/how-to-release.md index b86c6d0e7a..c880b28376 100644 --- a/docs/contributing/how-to-release.md +++ b/docs/contributing/how-to-release.md @@ -156,10 +156,11 @@ in the generated files too. ## MSW Visual Studio Official Builds To build official x86 and x64 shared binaries the following are prerequisites: - - Visual Studio 2012, 2013, 2015 - - Windows SDK 6.1, 7.1 (required for x64 builds for Visual Studio 2008, 2010) - - 7z (required for packaging the files) - - fciv (required for generating the checksums) + + - Visual Studio 2008, 2010, 2012, 2013, 2015, 2017, 2019 + - Windows SDK 6.1, 7.1 (required for x64 builds for Visual Studio 2008, 2010) + - 7z (required for packaging the files) + - fciv (required for generating the checksums) The VSxxxCOMNTOOLS environment variables are used to locate the tools required for Visual Studio 2012, 2013 and 2015. There are no Microsoft defined variables @@ -171,20 +172,32 @@ WINDOWS71SDK If either of these are blank they are set to the default install location. +For Visual Studio 2017 and 2019 the VSxxxxCOMNTOOLS environment variable is not +set by the installer as these two versions support multiple toolsets. +The build script will check the following in sequence: + - If VSxxxCOMNTOOLS is set (xxx=141: VS2017, xxx=142: VS2019) it is used as + the path to call VsDevCmd.bat to set up the environmet. + - If VSxxxCOMNTOOLS is not set, then the Visual Studio tool vswhere is used + to find the latest installed toolset for the compiler and the associated + VsDevCmd.bat file is used to set up the environment. + To build binaries for a single compiler, open a command prompt (for Visual Studio 2008 only an SDK 6.1 developer's command prompt must be used), cd to the build\tools\msvs folder and run the batch file 'officialbuild' with the vcXXX version number: -Visual Studio 2008 vc90 -Visual Studio 2010 vc100 -Visual Studio 2012 vc110 -Visual Studio 2014 vc120 -Visual Studio 2015 vc140 + Visual Studio 2008 vc90 + Visual Studio 2010 vc100 + Visual Studio 2012 vc110 + Visual Studio 2014 vc120 + Visual Studio 2015 vc140 + Visual Studio 2017 vc141 + Visual Studio 2019 vc142 This will build all of the x86 and x64 binaries for the selected compiler version, package them in 7z files and calculate the checksums. The 7z files and the checksums are output to the build\msw\packages folder. All of the compiler packages can be built at the same time by executing the -build\msw\tools\buildall.bat file (including Visual Studio 2000). +build\tools\msvs\buildall.bat file from a command prompt. Each build will be +launched in its own shell.