-
Notifications
You must be signed in to change notification settings - Fork 461
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
detecting vs2015 comes with vs2019 properly #1905
Comments
Thank you for the idea, I was not aware of this user scenario for the vcvars script. We may not be able to implement this immediately but we will monitor the community reactions (please give a thumbs up on the first entry of this GitHub issue) to find how this best fits in our backlog. |
@lygstate, I just tried -vcvars_ver=14.0 for a VS 2019 vcvarsall.bat and it points to a VS 14.0 installation (as opposed to some different toolset with the same version but placed within the VS 2019 location). And that VS 14.0 is detected already as a kit by this extension. Please give us a few more details about what is not working now, how do you run vcvars, what toolset is using and from where, is it not present in cmake-tools-kits.json already? |
Yeap, that's what I want, currently the vscode cmake tools didn't detect vs2015 by using -vcvars_ver=14.0 when vs 2019 installed. And detecting directly with "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" will fail building when the newest windows sdk are installed(The rc.exe can not found). |
Just to confirm, you are opening VSCode from a terminal where you didn't run vcvars yourself, right? You know that the extension does this when needed: run the appropriate vcvars script, from the correct location, with the correct arguments.... well ideally, there can always be bugs about that. So you have both VS 2019 and VS 2015 installed and you don't see any VS 2015 kits detected when scanning for kits? And before (before installing latest sdk if I understand correctly) VS 2015 was found by the kits scan? I haven't seen this, VS 2015 is properly detected where I tried this. I'll brainstorm more about why this can happen and I'll see what else I can try to reproduce this. What's a "cmake.loggingLevel": "Debug" logging in the "CMake/Build" output channel after scanning for kits? |
This is used to resolve the following issue:
|
May patch didn't fixed this issue, I need submit a fix |
This issue is now marked as 'stale-old' due to there being no activity on it for the past 720 days. Unless the 'stale-old' label is removed or the issue is commented on, this will be remain open for at least 14 days and then it may be closed. If you would like to make this issue exempt from getting stale, please add the 'stale-exempt' label. |
According to C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat
We can specify options for vs2015 or vs 2017
So we can detecting vs2015 proplery
The text was updated successfully, but these errors were encountered: