Before you can build keymaps, you need to install some software and set up your build environment. This only has to be done once no matter how many keyboards you plan to compile firmware for.
There are a few pieces of software you'll need to get started.
You'll need a program that can edit and save plain text files. If you're on Windows you can make do with Notepad, and on Linux you can use gedit. Both of these are simple but functional text editors. On macOS, be careful with the default TextEdit app: it will not save plain text files unless you explicitly select Make Plain Text from the Format menu.
You can also download and install a dedicated text editor like Sublime Text or VS Code. This is probably the best way to go regardless of platform, as these programs are specifically made for editing code.
?> Not sure which text editor to use? Laurence Bradford wrote a great introduction to the subject.
QMK Toolbox is an optional graphical program for Windows and macOS that allows you to both program and debug your custom keyboard. You will likely find it invaluable for easily flashing your keyboard and viewing debug messages that it prints.
qmk_toolbox.exe (portable) or
QMK.Toolbox.app.zip (portable) or
Linux and macOS come with unix shells you can execute already. You will only need to setup your build environment.
On Windows you will need to install MSYS2 or WSL and use those environments. Instructions for setting up MSYS2 are provided below.
We've tried to make QMK as easy to set up as possible. You only have to prepare your Linux or Unix environment, then let QMK install the rest.
?> If you haven't worked with the Linux/Unix command line before, there are a few basic concepts and commands you should learn. These resources will teach you enough to be able to work with QMK: Must Know Linux Commands Some Basic Unix Commands
You will need to install MSYS2, Git, and the QMK CLI.
Follow the installation instructions on the MSYS2 homepage.
Close any open MSYS2 terminals and open a new MSYS2 MinGW 64-bit terminal. NOTE: This is not the same as the MSYS terminal that opens when installation is completed.
After opening a new MSYS2 MinGW 64-bit terminal, make sure
pacman is up to date with:
You may be asked to close and reopen the window. Do this and keep running the above command until it says
there is nothing to do. Then run the following:
pacman -S git mingw-w64-x86_64-toolchain mingw-w64-x86_64-python3-pippython3 -m pip install qmk
You will need to install Homebrew. Follow the instructions on the Homebrew homepage.
After Homebrew is installed run this command:
brew install qmk/qmk/qmk
You will need to install Git and Python. It's very likely that you already have both, but if not, one of the following commands should install them:
Debian / Ubuntu / Devuan:
sudo apt install git python3 python3-pip
Fedora / Red Hat / CentOS:
sudo yum install git python3 python3-pip
Arch / Manjaro:
sudo pacman -S git python python-pip python-setuptools libffi
Install the global CLI to bootstrap your system:
python3 -m pip install --user qmk (on Arch-based distros you can also try the
qmk package from AUR (note: it's maintained by a community member):
yay -S qmk)
You will need to install Git and Python. It's possible that you already have both, but if not, run the following commands to install them:
pkg install git python3
Make sure that
$HOME/.local/bin is added to your
$PATH so that locally install Python packages are available.
Once installed, you can install QMK CLI:
python3 -m pip install --user qmk
After installing QMK you can set it up with this command:
In most situations you will want to answer Yes to all of the prompts.
?>Note on Debian, Ubuntu and their derivatives: It's possible, that you will get an error saying something like:
bash: qmk: command not found. This is due to a bug Debian introduced with their Bash 4.4 release, which removed
$HOME/.local/bin from the PATH. This bug was later fixed on Debian and Ubuntu. Sadly, Ubuntu reitroduced this bug and is yet to fix it. Luckily, the fix is easy. Run this as your user:
echo "PATH=$HOME/.local/bin:$PATH" >> $HOME/.bashrc && source $HOME/.bashrc
?>Note on FreeBSD: It is suggested to run
qmk setup as a non-
root user to start with, but this will likely identify packages that need to be installed to your base system using
pkg. However the installation will probably fail when run as an unprivileged user. To manually install the base dependencies, run
./util/qmk_install.sh either as
root, or with
sudo. Once that completes, re-run
qmk setup to complete the setup and checks.
?> If you already know how to use GitHub, we recommend that you create your own fork and use
qmk setup <github_username>/qmk_firmware to clone your personal fork. If you don't know what that means you can safely ignore this message.
Now that your QMK build environment is set up, you can build a firmware for your keyboard. Start by trying to build the keyboard's default keymap. You should be able to do that with a command in this format:
qmk compile -kb <keyboard> -km default
For example, to build a firmware for a Clueboard 66% you would use:
qmk compile -kb clueboard/66/rev3 -km default
When it is done you should have a lot of output that ends similar to this:
Linking: .build/clueboard_66_rev3_default.elf [OK]Creating load file for flashing: .build/clueboard_66_rev3_default.hex [OK]Copying clueboard_66_rev3_default.hex to qmk_firmware folder [OK]Checking file size of clueboard_66_rev3_default.hex [OK]* The firmware size is fine - 26356/28672 (2316 bytes free)
You can configure your build environment to set the defaults and make working with QMK less tedious. Let's do that now!
Most people new to QMK only have 1 keyboard. You can set this keyboard as your default with the
qmk config command. For example, to set your default keyboard to
qmk config user.keyboard=clueboard/66/rev4
You can also set your default keymap name. Most people use their GitHub username here, and we recommend that you do too.
qmk config user.keymap=<github_username>
After this you can leave those arguments off and compile your keyboard like this:
You are now ready to create your own personal keymap! Move on to Building Your First Firmware for that.