|
8 years ago | |
---|---|---|
.. | ||
keymaps | ed15973a3f Document size added by MIDI_ENABLE (~3800 bytes according to my experiments) | 8 years ago |
Makefile | ab4d7adbb9 Fix the template for the Makefile/rules.mk split | 8 years ago |
config.h | 525be99ee9 Split MIDI functionality into MIDI_BASIC and MIDI_ADVANCED | 8 years ago |
readme.md | 1f5838a286 Fix the keyboard template with new make syntax | 8 years ago |
rules.mk | c68e596f32 Implement faux-clicky feature | 8 years ago |
template.c | c1dfb636ef fixes quantum template (actually) | 9 years ago |
template.h | 13bb6b4b7f Backlight abstraction and other changes (#439) | 9 years ago |
For the full Quantum feature list, see the parent readme.
Download or clone the whole firmware and navigate to the keyboards/%KEYBOARD% 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 default
.
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.