Discussion:
[Scons-users] vswhere.. does it find all the versions of visual studio SCons users care about?
Bill Deegan
2018-02-21 00:35:57 UTC
Permalink
Greetings,

If you're using visual studio/visual c++ with scons, can you
download/install vswhere.exe

https://github.com/Microsoft/vswhere/releases/download/2.3.2/vswhere.exe

And run it as follows:

vswhere -all -legacy -property installationPath

Please reply with the versions it locates and/or doesn't locate that are
installed on your systems.

Trying to see if would be possible to use vswhere.exe to drop the somewhat
complicated logic we have now to find MSVS MSVC installs.

Thanks,
Bill
SCons Project Co-Manager
Eric Fahlgren
2018-02-21 02:20:08 UTC
Permalink
Home machine shows both installed versions correctly:

> c:/Temp/vswhere -all -legacy -property installationPath
C:\Program Files (x86)\Microsoft Visual Studio 14.0\
C:\Program Files (x86)\Microsoft Visual Studio 10.0\

I'll do a couple more at work tomorrow morning, as I have at least one with
the "VC 9.0 for Python 2" on it, which I suspect is the hard case.



On Tue, Feb 20, 2018 at 4:35 PM, Bill Deegan <***@baddogconsulting.com>
wrote:

> Greetings,
>
> If you're using visual studio/visual c++ with scons, can you
> download/install vswhere.exe
>
> https://github.com/Microsoft/vswhere/releases/download/2.3.2/vswhere.exe
>
> And run it as follows:
>
> vswhere -all -legacy -property installationPath
>
> Please reply with the versions it locates and/or doesn't locate that are
> installed on your systems.
>
> Trying to see if would be possible to use vswhere.exe to drop the somewhat
> complicated logic we have now to find MSVS MSVC installs.
>
> Thanks,
> Bill
> SCons Project Co-Manager
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
Bill Deegan
2018-02-21 02:38:28 UTC
Permalink
Fingers crossed it'll go back as far as VS 6.0.. ;)

On Tue, Feb 20, 2018 at 9:20 PM, Eric Fahlgren <***@gmail.com>
wrote:

> Home machine shows both installed versions correctly:
>
> > c:/Temp/vswhere -all -legacy -property installationPath
> C:\Program Files (x86)\Microsoft Visual Studio 14.0\
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\
>
> I'll do a couple more at work tomorrow morning, as I have at least one
> with the "VC 9.0 for Python 2" on it, which I suspect is the hard case.
>
>
>
> On Tue, Feb 20, 2018 at 4:35 PM, Bill Deegan <***@baddogconsulting.com>
> wrote:
>
>> Greetings,
>>
>> If you're using visual studio/visual c++ with scons, can you
>> download/install vswhere.exe
>>
>> https://github.com/Microsoft/vswhere/releases/download/2.3.2/vswhere.exe
>>
>> And run it as follows:
>>
>> vswhere -all -legacy -property installationPath
>>
>> Please reply with the versions it locates and/or doesn't locate that are
>> installed on your systems.
>>
>> Trying to see if would be possible to use vswhere.exe to drop the
>> somewhat complicated logic we have now to find MSVS MSVC installs.
>>
>> Thanks,
>> Bill
>> SCons Project Co-Manager
>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-***@scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
Jason Kenny
2018-02-21 02:45:57 UTC
Permalink
I am not sure how that is going to help much. This gives you an install root to start from, however the stuff under this is not 100% the same for the different versions of VS. I don’t this solves issues with the WinSdk as well.

Jason

From: Scons-users [mailto:scons-users-***@scons.org] On Behalf Of Bill Deegan
Sent: Tuesday, February 20, 2018 8:38 PM
To: SCons users mailing list <scons-***@scons.org>
Subject: Re: [Scons-users] vswhere.. does it find all the versions of visual studio SCons users care about?

Fingers crossed it'll go back as far as VS 6.0.. ;)

On Tue, Feb 20, 2018 at 9:20 PM, Eric Fahlgren <***@gmail.com<mailto:***@gmail.com>> wrote:
Home machine shows both installed versions correctly:

> c:/Temp/vswhere -all -legacy -property installationPath
C:\Program Files (x86)\Microsoft Visual Studio 14.0\
C:\Program Files (x86)\Microsoft Visual Studio 10.0\

I'll do a couple more at work tomorrow morning, as I have at least one with the "VC 9.0 for Python 2" on it, which I suspect is the hard case.


On Tue, Feb 20, 2018 at 4:35 PM, Bill Deegan <***@baddogconsulting.com<mailto:***@baddogconsulting.com>> wrote:
Greetings,
If you're using visual studio/visual c++ with scons, can you download/install vswhere.exe

https://github.com/Microsoft/vswhere/releases/download/2.3.2/vswhere.exe<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvswhere%2Freleases%2Fdownload%2F2.3.2%2Fvswhere.exe&data=02%7C01%7C%7Caa81537bc3b24cf2745208d578d4365d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636547775194932536&sdata=VVlcutsNeXnAaQjDDA791XoQT3M2QMFba8Kvj8fwYjs%3D&reserved=0>
And run it as follows:

vswhere -all -legacy -property installationPath
Please reply with the versions it locates and/or doesn't locate that are installed on your systems.
Trying to see if would be possible to use vswhere.exe to drop the somewhat complicated logic we have now to find MSVS MSVC installs.
Thanks,
Bill
SCons Project Co-Manager


_______________________________________________
Scons-users mailing list
Scons-***@scons.org<mailto:Scons-***@scons.org>
https://pairlist4.pair.net/mailman/listinfo/scons-users<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpairlist4.pair.net%2Fmailman%2Flistinfo%2Fscons-users&data=02%7C01%7C%7Caa81537bc3b24cf2745208d578d4365d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636547775194932536&sdata=2GDzX3Psx8SjZeyVtnu996LPngn1AHMD5Xf5RvGo48A%3D&reserved=0>


_______________________________________________
Scons-users mailing list
Scons-***@scons.org<mailto:Scons-***@scons.org>
https://pairlist4.pair.net/mailman/listinfo/scons-users<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpairlist4.pair.net%2Fmailman%2Flistinfo%2Fscons-users&data=02%7C01%7C%7Caa81537bc3b24cf2745208d578d4365d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636547775194932536&sdata=2GDzX3Psx8SjZeyVtnu996LPngn1AHMD5Xf5RvGo48A%3D&reserved=0>
Bill Deegan
2018-02-21 03:57:20 UTC
Permalink
SCons could drop all the logic which looks in the registry for locations
among other things. And a big pile of tests which would no longer be
needed.
We have to use vswhere to find VS2017 (and above) anyway.
A uniform approach to finding the install would be simpler.

On Tue, Feb 20, 2018 at 9:45 PM, Jason Kenny <***@live.com> wrote:

> I am not sure how that is going to help much. This gives you an install
> root to start from, however the stuff under this is not 100% the same for
> the different versions of VS. I don’t this solves issues with the WinSdk as
> well.
>
>
>
> Jason
>
>
>
> *From:* Scons-users [mailto:scons-users-***@scons.org] *On Behalf Of *Bill
> Deegan
> *Sent:* Tuesday, February 20, 2018 8:38 PM
> *To:* SCons users mailing list <scons-***@scons.org>
> *Subject:* Re: [Scons-users] vswhere.. does it find all the versions of
> visual studio SCons users care about?
>
>
>
> Fingers crossed it'll go back as far as VS 6.0.. ;)
>
>
>
> On Tue, Feb 20, 2018 at 9:20 PM, Eric Fahlgren <***@gmail.com>
> wrote:
>
> Home machine shows both installed versions correctly:
>
>
>
> > c:/Temp/vswhere -all -legacy -property installationPath
>
> C:\Program Files (x86)\Microsoft Visual Studio 14.0\
>
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\
>
>
>
> I'll do a couple more at work tomorrow morning, as I have at least one
> with the "VC 9.0 for Python 2" on it, which I suspect is the hard case.
>
>
>
>
>
> On Tue, Feb 20, 2018 at 4:35 PM, Bill Deegan <***@baddogconsulting.com>
> wrote:
>
> Greetings,
>
> If you're using visual studio/visual c++ with scons, can you
> download/install vswhere.exe
>
> https://github.com/Microsoft/vswhere/releases/download/2.3.2/vswhere.exe
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvswhere%2Freleases%2Fdownload%2F2.3.2%2Fvswhere.exe&data=02%7C01%7C%7Caa81537bc3b24cf2745208d578d4365d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636547775194932536&sdata=VVlcutsNeXnAaQjDDA791XoQT3M2QMFba8Kvj8fwYjs%3D&reserved=0>
>
> And run it as follows:
>
> vswhere -all -legacy -property installationPath
>
> Please reply with the versions it locates and/or doesn't locate that are
> installed on your systems.
>
> Trying to see if would be possible to use vswhere.exe to drop the somewhat
> complicated logic we have now to find MSVS MSVC installs.
>
> Thanks,
>
> Bill
>
> SCons Project Co-Manager
>
>
>
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpairlist4.pair.net%2Fmailman%2Flistinfo%2Fscons-users&data=02%7C01%7C%7Caa81537bc3b24cf2745208d578d4365d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636547775194932536&sdata=2GDzX3Psx8SjZeyVtnu996LPngn1AHMD5Xf5RvGo48A%3D&reserved=0>
>
>
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpairlist4.pair.net%2Fmailman%2Flistinfo%2Fscons-users&data=02%7C01%7C%7Caa81537bc3b24cf2745208d578d4365d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636547775194932536&sdata=2GDzX3Psx8SjZeyVtnu996LPngn1AHMD5Xf5RvGo48A%3D&reserved=0>
>
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
Mats Wichmann
2018-02-21 14:35:15 UTC
Permalink
On 02/20/2018 07:38 PM, Bill Deegan wrote:
> Fingers crossed it'll go back as far as VS 6.0.. ;)

is it really necessary to support things that old? VS6 dates back to the
last century.
Eric Fahlgren
2018-02-21 15:33:22 UTC
Permalink
Hmm, as I suspected, vswhere does not find the "most interesting" of the
compilers (at least for Python 2 users), namely the special 9.0
installation.

> p:/SCons/vswhere.exe -all -legacy -property installationPath
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional
C:\Program Files (x86)\Microsoft Visual Studio 14.0\
C:\Program Files (x86)\Microsoft Visual Studio 10.0\

> find c:/ -iname cl.exe
c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
Python/9.0/VC/bin/amd64/cl.exe
c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
Python/9.0/VC/bin/cl.exe
c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
Python/9.0/VC/bin/x86_amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX64/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX64/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx64/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx64/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx86/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual
Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx86/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/x86_amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_arm/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_arm/cl.exe
Bill Deegan
2018-02-21 15:40:06 UTC
Permalink
Eric,

Can you file an issue here:
https://github.com/Microsoft/vswhere

About vswhere not finding Visual C++ for Python?

If they can fix it (and any other versions we find missing which should be
simple for microsoft themselves to do), then that would be great!

On Wed, Feb 21, 2018 at 10:33 AM, Eric Fahlgren <***@gmail.com>
wrote:

> Hmm, as I suspected, vswhere does not find the "most interesting" of the
> compilers (at least for Python 2 users), namely the special 9.0
> installation.
>
> > p:/SCons/vswhere.exe -all -legacy -property installationPath
> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
> C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional
> C:\Program Files (x86)\Microsoft Visual Studio 14.0\
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\
>
> > find c:/ -iname cl.exe
> c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
> Python/9.0/VC/bin/amd64/cl.exe
> c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
> Python/9.0/VC/bin/cl.exe
> c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
> Python/9.0/VC/bin/x86_amd64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/
> Tools/MSVC/14.11.25503/bin/HostX64/x64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/
> Tools/MSVC/14.11.25503/bin/HostX64/x86/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/
> Tools/MSVC/14.11.25503/bin/HostX86/x64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/
> Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/
> Tools/MSVC/14.11.25503/bin/Hostx64/x64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/
> Tools/MSVC/14.11.25503/bin/Hostx64/x86/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/
> Tools/MSVC/14.11.25503/bin/Hostx86/x64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/
> Tools/MSVC/14.11.25503/bin/Hostx86/x86/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/amd64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/x86_amd64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_arm/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_amd64/cl.exe
> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_arm/cl.exe
>
>
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
Eric Fahlgren
2018-02-21 15:48:14 UTC
Permalink
Done:

https://github.com/Microsoft/vswhere/issues/134

On Wed, Feb 21, 2018 at 7:40 AM, Bill Deegan <***@baddogconsulting.com>
wrote:

> Eric,
>
> Can you file an issue here:
> https://github.com/Microsoft/vswhere
>
> About vswhere not finding Visual C++ for Python?
>
> If they can fix it (and any other versions we find missing which should be
> simple for microsoft themselves to do), then that would be great!
>
> On Wed, Feb 21, 2018 at 10:33 AM, Eric Fahlgren <***@gmail.com>
> wrote:
>
>> Hmm, as I suspected, vswhere does not find the "most interesting" of the
>> compilers (at least for Python 2 users), namely the special 9.0
>> installation.
>>
>> > p:/SCons/vswhere.exe -all -legacy -property installationPath
>> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
>> C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional
>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\
>> C:\Program Files (x86)\Microsoft Visual Studio 10.0\
>>
>> > find c:/ -iname cl.exe
>> c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
>> Python/9.0/VC/bin/amd64/cl.exe
>> c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
>> Python/9.0/VC/bin/cl.exe
>> c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for
>> Python/9.0/VC/bin/x86_amd64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools
>> /MSVC/14.11.25503/bin/HostX64/x64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools
>> /MSVC/14.11.25503/bin/HostX64/x86/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools
>> /MSVC/14.11.25503/bin/HostX86/x64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools
>> /MSVC/14.11.25503/bin/HostX86/x86/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/To
>> ols/MSVC/14.11.25503/bin/Hostx64/x64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/To
>> ols/MSVC/14.11.25503/bin/Hostx64/x86/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/To
>> ols/MSVC/14.11.25503/bin/Hostx86/x64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/To
>> ols/MSVC/14.11.25503/bin/Hostx86/x86/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/amd64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio
>> 10.0/VC/bin/x86_amd64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio
>> 14.0/VC/bin/amd64_arm/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio
>> 14.0/VC/bin/amd64_x86/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio
>> 14.0/VC/bin/x86_amd64/cl.exe
>> c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_arm/cl.exe
>>
>>
>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-***@scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>>
>
> _______________________________________________
> Scons-users mailing list
> Scons-***@scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
Jason Kenny
2018-02-21 16:32:56 UTC
Permalink
I see your point. I think we would want to use this to deal with new stuff, vs older stuff. I don't this vc6 is being used anymore ( I hope not) but I know the logic I have in parts for tool finding allows the old stuff to be unchanged and not break. I think in the SCons version of the MSVC tool allow the working old logic to handle older tools and let the vswhere handle newer drops. Ideally at some point older compiler like vc6 2002 2003 should be dropped. My worry is that rewriting the tool can break stuff that worked fine. I would prefer to add support for new stuff in a better way and nor break stuff that is working for people.

Jason
________________________________
From: Scons-users <scons-users-***@scons.org> on behalf of Eric Fahlgren <***@gmail.com>
Sent: Wednesday, February 21, 2018 9:48 AM
To: SCons users mailing list
Subject: Re: [Scons-users] vswhere.. does it find all the versions of visual studio SCons users care about?

Done:

https://github.com/Microsoft/vswhere/issues/134<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvswhere%2Fissues%2F134&data=02%7C01%7C%7C971acf85780443a181ef08d5794288f9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636548249022334707&sdata=F4tN%2BERWGSJE5b3YY1eAb80Sbua2MvCDGmTT7Di5XLU%3D&reserved=0>

On Wed, Feb 21, 2018 at 7:40 AM, Bill Deegan <***@baddogconsulting.com<mailto:***@baddogconsulting.com>> wrote:
Eric,

Can you file an issue here:
https://github.com/Microsoft/vswhere<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvswhere&data=02%7C01%7C%7C971acf85780443a181ef08d5794288f9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636548249022334707&sdata=N09kHyRmY5s4Fzr6M36L5OQ7Ubg0DKq%2BkZS%2BRJ9vC1c%3D&reserved=0>

About vswhere not finding Visual C++ for Python?

If they can fix it (and any other versions we find missing which should be simple for microsoft themselves to do), then that would be great!

On Wed, Feb 21, 2018 at 10:33 AM, Eric Fahlgren <***@gmail.com<mailto:***@gmail.com>> wrote:
Hmm, as I suspected, vswhere does not find the "most interesting" of the compilers (at least for Python 2 users), namely the special 9.0 installation.

> p:/SCons/vswhere.exe -all -legacy -property installationPath
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional
C:\Program Files (x86)\Microsoft Visual Studio 14.0\
C:\Program Files (x86)\Microsoft Visual Studio 10.0\

> find c:/ -iname cl.exe
c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for Python/9.0/VC/bin/amd64/cl.exe
c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for Python/9.0/VC/bin/cl.exe
c:/Program Files (x86)/Common Files/Microsoft/Visual C++ for Python/9.0/VC/bin/x86_amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX64/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX64/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx64/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx64/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx86/x64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.11.25503/bin/Hostx86/x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/x86_amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_arm/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_amd64/cl.exe
c:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_arm/cl.exe
Loading...