diff options
| author | Fred Sundvik <fsundvik@gmail.com> | 2016-08-27 21:01:46 +0300 |
|---|---|---|
| committer | Fred Sundvik <fsundvik@gmail.com> | 2016-08-27 21:01:46 +0300 |
| commit | cff26bc48413ec62d4f4a37e3a6ba34721e7670c (patch) | |
| tree | 84c78137841ad83036de7e36579bc7973b024f7a /keyboards/gh60/readme.md | |
| parent | a5b1af4999345239df5086351b52a5b4d2daa97e (diff) | |
| parent | 36b6a96596e6cbca879d5304a586e279c15b04a9 (diff) | |
Merge branch 'master' into fix_line_endings
Diffstat (limited to 'keyboards/gh60/readme.md')
| -rw-r--r-- | keyboards/gh60/readme.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/keyboards/gh60/readme.md b/keyboards/gh60/readme.md index ad042483d8..8c744bfd3c 100644 --- a/keyboards/gh60/readme.md +++ b/keyboards/gh60/readme.md @@ -48,13 +48,15 @@ Download or clone the whole firmware and navigate to the keyboards/gh60_rev_c fo 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`. +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 file named `<name>.c` in the keymaps folder, and see keymap document (you can find in top readme.md) and existent keymap files. -To build the firmware binary hex file with a keymap just do `make` with `KEYMAP` option like: +To build the firmware binary hex file with a keymap just do `make` with a keymap like this: + ``` -$ make KEYMAP=[default|jack|<name>] +$ make [default|jack|<name>] ``` + Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder. |