-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Unable to build with VS2017 after building with VS2015 #13398
Comments
watilde
added
build
Issues and PRs related to build files or the CI.
v8.x
windows
Issues and PRs related to the Windows platform.
labels
Jun 2, 2017
@seishun it's an edge case with a simple workaround (as you stated), but I'll see if there's a simple solution. |
2 tasks
Fix: #13485 |
refack
added a commit
to refack/node
that referenced
this issue
Jun 10, 2017
PR-URL: nodejs#13485 Fixes: nodejs#13398 Reviewed-By: James M Snell <[email protected]>
addaleax
pushed a commit
that referenced
this issue
Jun 12, 2017
PR-URL: #13485 Fixes: #13398 Reviewed-By: James M Snell <[email protected]>
It appeared to me, that the reason for the problem was a not needed VCTargetsPath system variable. After removing it, VS 2017 now sees V141 toolset. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
vcbuild
. You can cancel with Ctrl+C as soon as it starts building.vcbuild vs2017
.Result:
It works fine if I close cmd and re-open it. It seems building with VS2015 leaves some bad variables.
cc @refack
The text was updated successfully, but these errors were encountered: