summaryrefslogtreecommitdiff
path: root/keyboards/atomic/readme.md
diff options
context:
space:
mode:
authorcbbrowne <cbbrowne@cbbrowne.tor.int-afilias.info>2016-08-29 12:32:03 -0400
committercbbrowne <cbbrowne@cbbrowne.tor.int-afilias.info>2016-08-29 12:32:03 -0400
commitfba509780e70b20da998cf6caada228682965c5e (patch)
treedf21a76cdf5f9225fcae68abb0d72252fbd37e5d /keyboards/atomic/readme.md
parenta732003bfd1a780be0728cdacda71c0b3d8b59b3 (diff)
parent6d1e916851daa7bcbd8ef31b6fbc73cb369ef1f0 (diff)
Merge branch 'master' of https://github.com/jackhumbert/qmk_firmware
Diffstat (limited to 'keyboards/atomic/readme.md')
-rw-r--r--keyboards/atomic/readme.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/keyboards/atomic/readme.md b/keyboards/atomic/readme.md
index ab1e7ba1ff..674dcf113b 100644
--- a/keyboards/atomic/readme.md
+++ b/keyboards/atomic/readme.md
@@ -13,13 +13,14 @@ Download or clone the whole firmware and navigate to the keyboards/atomic folder
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 a file in the keymaps folder named `<name>.c` 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.