I think the msvc tool should discard versions where there is no cl tool since msvc (should) = Microsoft Visual C
Any idea how to update the appveyor config file to have it install cl ? -Bill On Sat, Aug 11, 2018 at 10:03 PM, Daniel Moody <dmoody...@gmail.com> wrote: > I was looking at one of our test in the appveyor CI and I noticed it was > failing due to the 'cl' executable not being found: > https://ci.appveyor.com/project/SCons/scons/build/3.0. > 1.205/job/yp0pg368ga5i033b#L141 > > This is a case where Visual Studio has been installed, but the C++ build > tools have not. SCons detects the Visual Studio installation and assumes > the C++ build tools will be there. > > Usually Visual Studio installs the c++ compiler by default so this is > generally not an issue, however for Visual Studio 2015, the c++ compiler > was not installed by default and when developing on systems where I was > using Visual Studio 2015 install, I ran into this issue myself a few times. > I would then need to go install the C++ compiler for that version to fix it. > > Is this a bug? Should SCons detect if the C++ compiler is installed along > with a Visual Studio version, and if the C++ compiler is not there, discard > that version from the list of available MSVS versions to use? > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev