-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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 fails with spaces in user directory #438
Comments
IMHO, It's so fascinating to see Windows people got interested by a new Terminal. Looks like 25 years ago with a fedora 2. |
Same here (really annoying this kind of issues still exists). |
Yep, this is a real bug. Should've escaped that commandline with quotes. I believe the bug is in one of the |
If someone wanted to dig into this and properly escape the commands in question, I'd happily review the PR :) |
Files of note in regards to fixing directories not being quoted in commands (either by quotation marks or
I am able to successfully build the CascadiaPackage project on x64 release after these changes. |
and
and counting... |
One possible solution: |
To be fair, that's a workaround, not a solution. |
I tried doing this but still get the same Error Edit: |
|
Your Windows build number: 10.0.17763.437
What you're doing and what's happening:
Trying to build using VS 2017 Enterprise, the build fails like this:
I suspect this is because of the space in my user folder. This also breaks razzle.cmd
The text was updated successfully, but these errors were encountered: