Skip to content
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

Closed
silverwind opened this issue Nov 25, 2015 · 6 comments
Closed

build: spaces in python path causes node_js2c build failure #4012

silverwind opened this issue Nov 25, 2015 · 6 comments
Labels
build Issues and PRs related to build files or the CI. windows Issues and PRs related to the Windows platform.

Comments

@silverwind
Copy link
Contributor

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 like C:\"Program Files"\.

@miklen you were able to fix this with reinstalling python to a non-space path, correct?

@silverwind 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
@bnoordhuis
Copy link
Member

I think that may have been fixed in the gyp update in 1d65b99 from end of last month.

@miklen
Copy link

miklen commented Nov 25, 2015

@silverwind yes, reinstalling to a non-spaced path fixed the problem.

@silverwind
Copy link
Contributor Author

@miklen were you building off master?

Not sure if the linked commit really fixed this, but a possible workaround could be to remove this line, like it's done already for targets like specialize_node_d in the same file.

@miklen
Copy link

miklen commented Nov 27, 2015

@silverwind yes.

@benjamingr
Copy link
Member

Was this fixed in #4841 or the subsequent/related PRs? Can someone confirm this is still an issue?

@silverwind
Copy link
Contributor Author

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
Labels
build Issues and PRs related to build files or the CI. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

4 participants