-
Notifications
You must be signed in to change notification settings - Fork 146
vs-build-tools-2017 (vs version 15) is not recognized #78
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
Comments
Do you see one that would be used for detecting BT 2017? |
I'm not sure if this is a result of cmake-js not supporting
Yields:
It appears this would work as an indicator |
Try with: cmake-js build -a x64 -r electron -v 1.6.0 -c "C:\Users\ehiller\AppData\Local\omega\system\cmake\bin\cmake.exe" -G "Visual Studio 15 2017 Win64" |
@unbornchikken That did it - built fine now. |
Hello, is there any chance to fix this bug? |
Any PR would be greatly appreciated, since I don't have VS 2017 by hand right now, and don't have too much time to setup a virtual environment. |
Maybe this helps: https://developercommunity.visualstudio.com/content/problem/2813/cant-find-registry-entries-for-visual-studio-2017.html |
@mkrivos Please run: reg query "HKLM\SOFTWARE\Classes\Installer\Dependencies\Microsoft.VisualStudio.MinShell.Msi,v15" What's the output? |
C:>reg query "HKLM\SOFTWARE\Classes\Installer\Dependencies\Microsoft.VisualStudio.MinShell.Msi,v15" HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\Microsoft.VisualStudio.MinShell.Msi,v15 HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\Microsoft.VisualStudio.MinShell.Msi,v15\Dependents |
Please try master. |
copy vsDetect from master into node_modules and try -> seems to be OK.
info TOOL Using Visual Studio 15 2017 Win64 generator. |
Fixed as of 3.5.0. |
Doesn't seem to be fixed for me. I have VS2017 installed, and I also have the 2015 build tools installed, cmake-js detects neither. node-gyp works fine though. |
cmake-js 3.6.2 Still getting OMG There is no Visual C++ compiler installed |
Just stumbled across this. Note that the linked Developer Community page uses undocumented, unsupported registry key paths that were valid (documented, supported) for past versions but not for Visual Studio 2017. I worked with the CMake community to provide the necessary capabilities in our query API, for which CMake added support in commit Kitware/CMake@9ffb353. I came across this because I'm looking to create a node native module for easier consumption with possible Unicode (encoded as UTF8) output that generally causes problems for console applications. |
In a continuation of #46 - it appears that build tools 2017 is not found
ERR! OMG Error: There is no Visual C++ compiler installed. Install Visual C++ Build Toolset or Visual Studio.
From what I can tell,
cmake-js
looks in in vsDetect in the registry keyVisual Studio 2017 build tools does not have a registry key there, although there are others, that particular one does not exist.
The text was updated successfully, but these errors were encountered: