-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
build: spaces in python path causes node_js2c build failure #4012
Comments
silverwind
added
windows
Issues and PRs related to the Windows platform.
build
Issues and PRs related to build files or the CI.
labels
Nov 25, 2015
I think that may have been fixed in the gyp update in 1d65b99 from end of last month. |
@silverwind yes, reinstalling to a non-spaced path fixed the problem. |
@silverwind yes. |
This was referenced Jan 24, 2016
Was this fixed in #4841 or the subsequent/related PRs? Can someone confirm this is still an issue? |
Yeah it was fixed by #4841, forgot to close. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #3984 (comment). I assume the user has installed Python under
C:\Program Files\
.Also found http://stackoverflow.com/questions/17300638/building-node-js-v0-10-12-on-windows which points to
node_js2c.vcxproj
being generated with non-escaped paths. I think to correct way to handle this would be to quote the spaced path likeC:\"Program Files"\
.@miklen you were able to fix this with reinstalling python to a non-space path, correct?
The text was updated successfully, but these errors were encountered: