From 2c63214c7d331f6ace4a3dd9a9ecd1fc20b2ce6a Mon Sep 17 00:00:00 2001
From: Pete Johanson <peter@peterjohanson.com>
Date: Wed, 10 Jun 2020 00:13:55 -0400
Subject: [PATCH] A few more missing build steps.

---
 docs/docs/dev-setup.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/docs/dev-setup.md b/docs/docs/dev-setup.md
index 302a75ab..ea6772dd 100644
--- a/docs/docs/dev-setup.md
+++ b/docs/docs/dev-setup.md
@@ -36,6 +36,7 @@ apt-get install -y \
 	gcc-multilib \
 	libtool \
 	make \
+    ninja-build \
     cmake \
 	python3-dev \
 	python3-pip \
@@ -115,6 +116,12 @@ west update
 west zephyr-export
 ```
 
+#### Install Zephyr Python Dependencies
+
+```bash
+pip3 install --user -r zephyr/scripts/requirements.txt
+```
+
 ### Environment Variables
 
 By default, the Zephyr™ SDK will create a file named `~/.zephyrrc` with the correct environment variables to build ZMK.
@@ -131,7 +138,7 @@ source zmk/zephyr/zephyr-env.sh
 #### All Shells
 
 To load the environment variables for your shell every time,
-append the existing `~/.zephyrrc` file to your shell's RC file, e.g.
+append the existing `~/.zephyrrc` file to your shell's RC file and then start a new shell.
 
 ##### Bash