-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMake scan kits for VS2017 found question mark. #1104
Comments
What VS 2017 SKU did you install (maybe you can still remember the link). Where is your VS 2017 installed on your computer? What version does VS have (see windows-about)? |
I didn't install VS 2017, just the vs 2017 compier in visual studio 2019 |
Interesting, I wasn't aware of that possibility. I just tried it and I don't reproduce the "???". In my case it's not detected at all, which of course we can look at this and fix it for 1.4 but I'm still curious how you are able to have them detected, even with the "???" in the name. What CMake Tools version do you have? What 2019 SKU, Enterprise or something else? I tried this, on a computer with only 2019 Enterprise: VS Installer --> Modify --> Individual Components --> Search --> type 2017 --> find several and checked all --> let them install. |
|
Which vswhere.exe should execute, I can execute locally. |
I am using Chiense version of Visual Studio 2019, |
Try |
There is also a version that comes with the CMake Tools extension:
|
Yeap,you are all right, the source of the problem are vswhere
But in cmake-tools
because we force the encoding of the vswhere stdout to be utf8 but the fact on my computer, the stdout encoding are GBK |
Newer versions of vswhere support a |
CMake Tools 1.4.0 Beta is available on GitHub. Please try it out and let us know if you encounter any issues. |
fixed |
The found vs 2017 Toolchain have question mark
Brief Issue Summary
Expected:
Apparent Behavior:
CMake Tools Log
Developer Tools Log
Platform and Versions
Other Notes/Information
The text was updated successfully, but these errors were encountered: