I am building CEF for integrating in another product, using VS 2017. After a BSOD requiring reinstall, I have now only VS 2019 Community Edition, but with 2017 tools installed.
My build script contains
- Code: Select all
SET DEPOT_TOOLS_WIN_TOOLCHAIN=0
SET GYP_MSVS_VERSION=2017
SET GYP_MSVS_OVERRIDE_PATH=G:\bin\vs\2017\pro
set VS2017_INSTALL=G:\bin\vs\2017\pro
pointing to the specific path and version of VS 2017 - now gone as installed program (the disk content of the pre-Windows reset installation is intact, but not as installed - just the files).
So, the questions:
1. Can I use GYP_MSVS_VERSION=2017 and the GYP_MSVS_OVERRIDE_PATH + VS2017_INSTALL pointing to the VS 2019 Community Edition?
Will this know to build using the toolset v141 (cl 2017) tools using the installed VS from that location, or the VS version will be forced to whatever product is detected there (2019, in this case) and will build with toolset v142?
Something similar when creating a solution in VS2019 but instruct projects to build with Platform Toolset v141.
I saw in chromium/src/build/vs_toolchain.py there is the mapping between GYP_MSVS_VERSION and MSVC_TOOLSET_VERSION
or, as an alternative
2. Can the previous VS 2017 disk files be used by the build as-is (i.e. without actually having VS 2017 installed as a product) ?
There are setups for building various systems which simply copy a VS installation directory and then use it only based on its disk location, i.e. without relying on registry keys, default installation paths etc. - just knowing the build tools are in Q:\whatever\acme-2017-tools.