# Get started with Particle Workbench **URL:** \ **Category:** Tutorials\ **Created:** [June 3, 2019, 4:03pm UTC](https://community.particle.io/t/get-started-with-particle-workbench/50143 "2019-06-03T16:03:56Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![m\_m](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/m_m/32/18365_2.png) [@m\_m](https://community.particle.io/u/m_m)\ **Post date:** [July 1, 2019, 3:30pm UTC](https://community.particle.io/t/get-started-with-particle-workbench/50143/16 "2019-07-01T15:30:08Z")
> Should I clean the build every time I switch to compile the different Gen3 devices? yes. workbench tries to detect a "dirty" state _at launch_ and will prompt you to clean if necessary but in general we say "when in doubt, clean" 👍 > What I’m seeing is that your folder path cannot have any whitespace or blank spaces or it will not work. yes, an unfortunate limitation of our current build system - more info here: > [@\[issue\] spaces in project path cause build errors (was: Workbench Build Errors)](https://community.particle.io/t/issue-spaces-in-project-path-cause-build-errors-was-workbench-build-errors/48767/8): > > is this the actual location of your project? “location”: “/home/john/Projects for ParticleIO/WorkbenchWorkspaceLocal/BLINKERLOCAL2” if so, we don’t support spaces in file paths since the underlying make system does not handle them well (if at all) - see: this would explain the error(s) you are seeing - e.g: recipe for targetParticleIO/WorkbenchWorkspaceLocal/BLINKERLOCAL2/target//Projects’ …/…/…/build/module.mk:235: target for' given more than once in the same rule. just to confirm, can … --- _[View the full topic](https://community.particle.io/t/get-started-with-particle-workbench/50143)._