aboutsummaryrefslogtreecommitdiff
path: root/keyboards/gh60/readme.md
diff options
context:
space:
mode:
Diffstat (limited to 'keyboards/gh60/readme.md')
-rw-r--r--keyboards/gh60/readme.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/keyboards/gh60/readme.md b/keyboards/gh60/readme.md
index ad042483d..8c744bfd3 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
48Depending on which keymap you would like to use, you will have to compile slightly differently. 48Depending on which keymap you would like to use, you will have to compile slightly differently.
49 49
50### Default 50### Default
51To build with the default keymap, simply run `make`. 51To build with the default keymap, simply run `make default`.
52 52
53### Other Keymaps 53### Other Keymaps
54Several 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. 54Several 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.
55 55
56To build the firmware binary hex file with a keymap just do `make` with `KEYMAP` option like: 56To build the firmware binary hex file with a keymap just do `make` with a keymap like this:
57
57``` 58```
58$ make KEYMAP=[default|jack|<name>] 59$ make [default|jack|<name>]
59``` 60```
61
60Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder. 62Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.