fauxpark
e96cac0814
Cleanup rules.mk for 32U4 keyboards, L-M (#7120)
* Cleanup rules.mk for 32U4 keyboards, L-M * Move some stuff to keyboard level |
4 years ago | |
---|---|---|
.. | ||
keymaps/default | Remove/migrate action_get_macro()s from default keymaps (#5625) | 4 years ago |
config.h | Replace DEBOUNCING_DELAY (deprecated) with DEBOUNCE (#5997) | 5 years ago |
info.json | Keyboard: LFKPad refactor and Configurator support (#3439) | 5 years ago |
lfkpad.c | Keyboard: LFKPad refactor and Configurator support (#3439) | 5 years ago |
lfkpad.h | Keyboard: LFKPad refactor and Configurator support (#3439) | 5 years ago |
readme.md | Fixed dead links (#2451) | 6 years ago |
rules.mk | Cleanup rules.mk for 32U4 keyboards, L-M (#7120) | 4 years ago |
For the full Quantum feature list, see the parent readme.md.
Download or clone the whole firmware and navigate to the keyboards/bluepad 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.
To build with the default keymap, simply run make
.
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 keymap
option like:
$ make keymap=[default|jack|<name>]
Keymaps follow the format keymap.c and are stored in folders in the keymaps
folder, eg keymaps/my_keymap/