<Resent as the first message did not go to the developer list as well.>
Thanks for that. Actually, I do want to know.
AFAIK, the handling of 14.0 is quite different as it is not installed
side-by-side in 2017 and 2019. I'm not sure because I already had 2015
installed, but I believe the installation option in 2017 may be to install
the 2015 tools "normally" (i.e., outside of the 2017 folder).
For the 14.0 toolset with 2017 and 2019 there is "special case" handling
and a specific batch file: vcvars140.bat. While you may not be able to
install the 2015 tools with the 2019 installed, you can still pass "14.0"
as the toolset. In 2019, vcvars140.bat is in the
folder "Common7\Tools\vsdevcmd\ext\vcvars\vcvars140.bat". The vcvars140.bat
file queries the registry to find the installation location of the 2015
tools (comments extracted from my working version):
# vcvars140.bat compatible registry queries:
# HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\SxS\VC7 /v "14.0"
# HKLM\SOFTWARE\Microsoft\VisualStudio\SxS\VC7 /v "14.0"
On Mon, Aug 10, 2020 at 8:36 PM Mats Wichmann <m...@wichmann.us> wrote:
> On 8/10/20 6:03 PM, Joseph Brill wrote:
>
> > Yes. I believe the number is 9 separate product installations for 2017
> > (build tools, express, community, professional, and enterprise) and 2109
> > (build tools, community, professional, and enterprise). I don't have
> > access to professional or enterprise versions and a I believe the
> > installer for 2017 build tools is rarer than hen's teeth (although it
> > may be available via Chocolatey). As far as I know, there is not an
> > express version of 2019. Locally, I have been using four installations
> > for testing of the 14.1 (14.16) toolsets: 2017 Community, 2017 Express,
> > 2019, Community, and 2019 Build Tools.
>
> Only minor correction: you can get eight via just the standard installer
> - build tools 2017 is not rare at all; while express (yes, "expressly"
> discontinued after 2017) is quite hard to find, and you can't get at it
> through the standard VS installer - until you actually have it
> installed, then the installed VS 2017 installer will let you manipulate
> it, but it's invisible otherwise.
>
> > It is possible to specify the 2015 toolset (14.0) via MSVC 2017 and MSVC
> > 2019 as well.
>
> the installation policy seems to be you get one toolset version from the
> previous major release, only. I don't "know" this (as I've read no doc
> or anything), deducing this from looking at my one machine with a bunch
> of different VCs installed:
>
> the 2017 VS Installer offers me "2015.3 v14.00" v140 toolset, along with
> v141 14.11 through 14.16.
>
> The 2019 VS installer offers me v141 14.16, along with v142 14.20
> through 14.27 - note no toolset for 2015 here.
>
>
> all this is probably getting down to "more than anyone wants to know" :)
>
>
_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev
