Where Does Zephyr Store the Workspace and Toolchain?
Zephyr lives in a west workspace you created, with the SDK in ~/.zephyrproject or /opt and builds per app.
Last updated
Zephyr has no installer location because you assemble the workspace yourself with west init. That workspace folder holds the RTOS, modules and your applications side by side.
The SDK sits apart from it, wherever the setup script put it. Build outputs land in a build directory inside each application, so wiping and rebuilding one app never disturbs the rest.
Where Zephyr stores this, by platform
~/zephyrproject
Conventional workspace root with zephyr, modules and bootloader inside. SDK commonly at ~/.local/zephyr-sdk-0.x or /opt. Each app builds into its own build folder.
~/zephyrproject
Same layout on Mac. Case sensitive quirks bite on default filesystems, so keep the workspace on a case sensitive volume if builds act strangely.
%USERPROFILE%\zephyrproject
Same tree on Windows. Long paths break builds silently, so the short default location beats a nested Documents folder.
Frequently asked questions
where are zephyr build outputs
In the build directory inside your application folder, with zephyr.hex and zephyr.bin at its root when the build succeeds. Delete it for a clean rebuild.
where is the zephyr sdk installed
Wherever you extracted it, commonly ~/.local or /opt on Linux. The ZEPHYR_SDK_INSTALL_DIR variable records the choice for CMake.
Notice an outdated path? Let us know.