b05c0e46c6
* Add default value for IS_COMMAND for COMMAND feature * Cleanup and consistency * Update Templates to reflect change * Fix IS_COMMAND in template * Fix IS_COMMAND define * Use consistent IS_COMMAND block in templates * Remove unnecessary `#undef IS_COMMAND` directives * Fix compile issue on orthodox * Reomve IS_COMMAND option for newer boards * Remove all existing definitions of IS_COMMAND if they use default LSHIFT and RSHIFT setting * Remove a couple of additional IS_COMMAND defines * Remove remaining redundant IS_COMMAND definitions * Remove #undef IS_COMMAND from orthodox:drashna and whitefox:konstantin * Remove multiple empty lines in modified config.h files * Update additional boards * Reomve IS_COMMAND from newer boards * Update Alice keyboard * Remove IS_COMMAND from additional boards Jan 24th edition |
||
|---|---|---|
| .. | ||
| keymaps/default | ||
| config.h | ||
| info.json | ||
| nakey.c | ||
| nakey.h | ||
| readme.md | ||
| rules.mk | ||
readme.md
naKey
Firmware for custom keyboard
Keyboard Maintainer: James Underwood
Hardware Supported: naKey
Hardware Availability: ckeys.org
To build this keyboard, follow the build guide.
Make example for this keyboard (after setting up your build environment):
make ckeys/nakey:default
See build environment setup then the make instructions for more information.
Quantum MK Firmware
For the full Quantum feature list, see the parent readme.
Building
Download or clone the whole firmware and navigate to the root folder. Once your dev env is setup, you'll be able to type make ckeys/nakey:default to generate your .hex - you can then use the Teensy Loader to program your .hex file.
(Note: replace naKey with the name of your keyboard.)
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 ckeys/nakey: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. Create a readme.md and a keymap.c file to complete your new keymap. When you are done your file tree should look like this:
qmk_firmware/keyboard/keymaps/config.h(optional)keymap.creadme.mdrules.mk(optional)
To build the firmware binary hex file with a keymap just do make with a keymap like this:
$ make naKey-[default|jack|<name>]