@ -178,6 +179,20 @@ Homebrew is required to install the system dependencies. If you haven't done so,
@@ -178,6 +179,20 @@ Homebrew is required to install the system dependencies. If you haven't done so,
This setup leverages the same [image which is used by the GitHub action](https://github.com/zmkfirmware/zephyr-west-action) for local development. Beyond the benefits of [dev/prod parity](https://12factor.net/dev-prod-parity), this approach is also the easiest to set up. No toolchain or dependencies are necessary when using Docker; the container image you'll be using already has the toolchain installed and set up to use.
1. Install [Docker Desktop](https://www.docker.com/products/docker-desktop) for your operating system.
3. Install the [Remote - Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
:::info
The docker container includes `west` and the compilation toolchain. If you're using docker and VS Code, you can skip right to [Source Code](#source-code).
:::
</TabItem>
</OsTabs>
@ -349,12 +364,63 @@ Since ZMK is built as a Zephyr™ application, the next step is
@@ -349,12 +364,63 @@ Since ZMK is built as a Zephyr™ application, the next step is
to use `west` to initialize and update your workspace. The ZMK
Zephyr™ application is in the `app/` source directory:
#### Step into the repository
<OsTabs>
<TabItemvalue="debian">
```sh
cd zmk
```
</TabItem>
<TabItemvalue="raspberryos">
```sh
cd zmk
```
</TabItem>
<TabItemvalue="fedora">
```sh
cd zmk
```
</TabItem>
<TabItemvalue="mac">
```sh
cd zmk
```
</TabItem>
<TabItemvalue="win">
```sh
cd zmk
```
</TabItem>
<TabItemvalue="docker">
Open the `zmk` checkout folder in VS Code. The repository includes a configuration for containerized development, so an alert will pop up:
![VS Code Dev Container Configuration Alert](assets/dev-setup/vscode_devcontainer.png)
Click `Reopen in Container` in order to reopen the VS Code with the running container.
The first time you do this on your machine, it will pull the docker image down from the registry and build the container. Subsequent launches are much faster!
:::caution
All subsequent steps must be performed from the VS Code terminal _inside_ the container.
:::
</TabItem>
</OsTabs>
#### Initialize West
```sh
@ -373,6 +439,17 @@ section again for links to how to do this
@@ -373,6 +439,17 @@ section again for links to how to do this
west update
```
:::tip
This step pulls down quite a bit of tooling. Go grab a cup of coffee, it can take 10-15 minutes even on a good internet connection!
:::
:::info
If you're using Docker, you're done with setup! You must restart the container at this point. The easiest way to do so is to close the VS Code window, verify that the container has stopped in Docker Dashboard, and reopen the container with VS Code.
Once your container is restarted, proceed to [Building and Flashing](./dev-build.md).