Desktop not compiling if directory path contains a space
See original GitHub issueDescribe the bug
If path of Desktop repo contains a space, then Desktop is not compiled, returning an error.
Version & OS
Github Desktop: development branch, OS: Windows 10
Steps to reproduce the behavior
- Compile Desktop with
yarn build:dev
Expected behavior
Compiling without error.
Actual behavior
Generates an error (image below) during compile.
Screenshots
Additional context
If path doesn’t contain spaces (in my case) it compiles correctly. If the error isn’t repairable, I suggest to add a note in “docs/contributing/setup.md”. Or add the same note into troubleshooting section.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Issue compiling on Windows when path contains spaces #1279
Every time I've tried to compile Tiled I get a LNK1104 error that "intermediate.tiled.exe.manifest" could not be opened.
Read more >mingw make can't handle spaces in path? - Stack Overflow
The common way to do it in Linux/UNIX is to escape each space with a backslash, like: /c/Documents\ and\ Settings/User However, this doesn't ......
Read more >Solved: Folder names not working with spaces (sometimes!)
Solved: Hello, Creating my first flow, to auto-save Gmail attachments to OneDrive. It is (almost) working. In "OneDrive Create File" I use.
Read more >"make" command does not work in directories containing ...
1 Answer 1 · 1. It is a feature!! Spaces if directory- and file-names has never been good prattice in Linux or Unix....
Read more >Error: The Working Directory location cannot have a space in ...
1. Click Start > Settings > Control Panel. · 2. Double-click the System icon. · 3. Click the Advanced tab. · 4. Set...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rafeca how about opening a PR to update only the cross-zip dependency and close this issue? I know it’s not the best practice to edit manually the
yarn.lock
file, but I think it won’t break anything.Sounds good to me as a temporary fix, so feel free to send the PR!
Note that
electron-packager
is moving away fromcross-zip
toextract-zip
(see https://github.com/electron/electron-packager/pull/1139), but either way upgradingcross-zip
to v3.1.0 should be fine now.