This page describes setting up the build environment for QMK. These instructions cover AVR processors (such as the atmega32u4.)
To ensure you are always up to date, you can just run
sudo util/install_dependencies.sh. That should always install all the dependencies needed. This will run
You can also install things manually, but this documentation might not be always up to date with all requirements.
The current requirements are the following, but not all might be needed depending on what you do. Also note that some systems might not have all the dependencies available as packages, or they might be named differently.
build-essential gcc unzip wget zip gcc-avr binutils-avr avr-libc dfu-programmer dfu-util gcc-arm-none-eabi binutils-arm-none-eabi libnewlib-arm-none-eabi git
Install the dependencies with your favorite package manager.
sudo apt-get update sudo apt-get install gcc unzip wget zip gcc-avr binutils-avr avr-libc dfu-programmer dfu-util gcc-arm-none-eabi binutils-arm-none-eabi libnewlib-arm-none-eabi
If you’re on NixOS, or have Nix installed on Linux or macOS, run
nix-shell from the repository root to get a build environment.
By default, this will download compilers for both AVR and ARM. If you don’t need both, disable the
arm arguments, e.g.:
nix-shell --arg arm false
If you’re using homebrew, you can use the following commands:
brew tap osx-cross/avr brew tap PX4/homebrew-px4 brew update brew install avr-gcc brew install dfu-programmer brew install gcc-arm-none-eabi
This is the recommended method. If you don’t have homebrew, install it! It’s very much worth it for anyone who works in the command line. Note that the
make install portion during the homebrew installation of avr-libc can take over 20 minutes and exhibit high CPU usage.
The best environment to use, for Windows Vista through any later version (tested on 7 and 10,) is msys2.
$ cd /c/qmk_firmware
util/msys2_install.shand follow the prompts
These are the old instructions for Windows 10. We recommend you use MSYS2 as outlined above.
If you have Windows 10 with Creators Update or later, you can build and flash the firmware directly. Before the Creators Update, only building was possible. If you don’t have it yet or if are unsure, follow these instructions.
In addition to the Creators Update, you need Windows 10 Subystem for Linux, so install it following these instructions. If you already have the Windows 10 Subsystem for Linux from the Anniversary update it’s recommended that you upgrade it to 16.04LTS, because some keyboards don’t compile with the toolchains included in 14.04LTS. Note that you need to know what your are doing if you chose the
sudo do-release-upgrade method.
If you already have cloned the repository on your Windows file system you can ignore this section.
You will need to clone the repository to your Windows file system using the normal Git for Windows and not the WSL Git. So if you haven’t installed Git before, download and install it. Then set it up, it’s important that you setup the e-mail and user name, especially if you are planning to contribute.
Once Git is installed, open the Git bash command and change the directory to where you want to clone QMK, note that you have to use forward slashes, and that your c drive is accessed like this
/c/path/to/where/you/want/to/go. Then run
git clone --recurse-submodules https://github.com/qmk/qmk_firmware, this will create a new folder
qmk_firmware as a subfolder of the current one.
The Toolchain setup is done through the Windows Subsystem for Linux, and the process is fully automated. If you want to do everything manually, there are no other instructions than the scripts themselves, but you can always open issues and ask for more information.
qmk_firmware. Note that the paths start with
/mnt/in the WSL, so you have to write for example
util/wsl_install.shand follow the on-screen instructions.
util/wsl_install.shagain to get all the newest updates.
These are the old instructions for Windows Vista and later. We recommend you use MSYS2 as outlined above.
1-setup-path-winbatch script to run it. You’ll need to accept a User Account Control prompt. Press the spacebar to dismiss the success message in the command prompt that pops up.
2-setup-environment-winbatch script, select “Run as administrator”, and accept the User Account Control prompt. This part may take a couple of minutes, and you’ll need to approve a driver installation, but once it finishes, your environment is complete!
If you have trouble and want to ask for help, it is useful to generate a Win_Check_Output.txt file by running
Win_Check.bat in the
If this is a bit complex for you, Docker might be the turn-key solution you need. After installing Docker, run the following command at the root of the QMK folder to build a keyboard/keymap:
# You'll run this every time you want to build a keymap # modify the keymap and keyboard assigment to compile what you want # defaults are ergodox/default docker run -e keymap=gwen -e keyboard=ergodox_ez --rm -v $('pwd'):/qmk:rw edasque/qmk_firmware # On windows docker seems to have issue with VOLUME tag in Dockerfile, and $('pwd') won't print a windows compliant path, use full path instead like this docker run -e keymap=default -e keyboard=ergobox_ez --rm -v D:/Users/Sacapuces/Documents/Repositories/qmk:/qmk:rw edasque/qmk_firmware
This will compile the targeted keyboard/keymap and leave it in your QMK directory for you to flash.
If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that’s ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the vagrant guide.