4cdcbdb861
* Remove all Makefiles from the keyboards directory. * update keymaps added in the last 8 days * Ignore keyboard/keymap makefiles * update hand_wire to reflect our new Makefile-less reality * Update the make guide to reflect the new reality * move planck keymap options to rules.mk * update planck keymaps 4real * trigger travis * add back build_keyboard.mk * restore changes to build_keyboard |
7 years ago | |
---|---|---|
.. | ||
keymaps/default | 7 years ago | |
Makefile | 8 years ago | |
config.h | 8 years ago | |
pilcrow.c | 8 years ago | |
pilcrow.h | 8 years ago | |
readme.md | 8 years ago | |
rules.mk | 8 years ago |
readme.md
pilcrow keyboard firmware
Quantum MK Firmware
For the full Quantum feature list, see the parent readme.
Building
Download or clone the whole firmware and navigate to the keyboards/pilcrow folder. Once your dev env is setup, you'll be able to type make
to generate your .hex - you can then use the Teensy Loader to program your .hex file.
Depending on which keymap you would like to use, you will have to compile slightly differently.
Default
To build with the default keymap, simply run make default
.
Other Keymaps
Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create a folder with the name of your keymap in the keymaps folder, and see keymap documentation (you can find in top readme.md) and existant keymap files.
To build the firmware binary hex file with a keymap just do make
with a keymap like this:
$ make [default|jack|<name>]
Keymaps follow the format <name>.c and are stored in the keymaps
folder.