The latest update of Workbench includes support for spaces in project directories and toolchain directories (where Device OS is installed). Local compilation now works in case the Windows user directory has a space. When compiling, a directory like C:\Users\Example Name\Projects\widget will become C:\Users\EXAMPL~1\Projects\widget
Path with spaces are still not supported on Linux and Mac as a similar workaround is not possible.
Let us know if you still run into issues with local compilation on Windows.
Hey @jvanier! Thanks for the quick response! I'm still seeing the issue on Windows 10.0.19045. Latest version of vscode as well as Particle Workbench v1.16.14. My Windows user path has a space in it. Here's the error:
* Executing task: make -f 'C:\Users\FirstName LastName\.particle\toolchains\buildscripts\1.15.0\Makefile' compile-user
:::: COMPILING APPLICATION
make -f LastName\.particle\toolchains\buildscripts\1.15.0\Makefile compile-user-steps
make[1]: Entering directory '/cygdrive/c/repos/HumidityReadout'
make[1]: LastName\.particle\toolchains\buildscripts\1.15.0\Makefile: No such file or directory
make[1]: *** No rule to make target 'LastName\.particle\toolchains\buildscripts\1.15.0\Makefile'. Stop.
make[1]: Leaving directory '/cygdrive/c/repos/HumidityReadout'
make: *** [C:\Users\FirstName LastName\.particle\toolchains\buildscripts\1.15.0\Makefile:87: compile-user] Error 2
* The terminal process "C:\Users\FirstName LastName\.particle\toolchains\buildtools\1.1.1\bin\bash.exe '-c', 'make -f 'C:\Users\FirstName LastName\.particle\toolchains\buildscripts\1.15.0\Makefile' compile-user'" terminated with exit code: 2.
* Press any key to close the terminal.
I found a tutorial that gave me enough confidence to dive into regedit and successfully remove the space from my user path. Now compilation works fine!