|
|
7 tahun lalu | |
|---|---|---|
| .. | ||
| keymaps | 67adc29aa3 Remove empty fn_actions[] | 7 tahun lalu |
| config.h | b05c0e46c6 Adds a default value for IS_COMMAND for COMMAND feature (#4301) | 7 tahun lalu |
| readme.md | d28fb63fac updated drashna's keymaps (#1769) | 8 tahun lalu |
| rules.mk | 19a1fbaca2 Better non-Linux support (#2524) | 7 tahun lalu |
| woodpad.c | d28fb63fac updated drashna's keymaps (#1769) | 8 tahun lalu |
| woodpad.h | d28fb63fac updated drashna's keymaps (#1769) | 8 tahun lalu |
For the full Quantum feature list, see the parent readme.
Download or clone the whole firmware and navigate to the keyboards/woodpad 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.