diff options
| author | Seth Chandler <sethbc@sethbc.org> | 2016-07-17 10:37:45 -0400 |
|---|---|---|
| committer | Seth Chandler <sethbc@sethbc.org> | 2016-07-17 10:37:45 -0400 |
| commit | d40d18ab1ae8a1ef9feb408e43d4b840d37998a8 (patch) | |
| tree | 3b0fe5f0f04e38fdf1110e6efe208984327388c3 | |
| parent | f6aeaac5b549ff111f24b6d07c33a3f29b785823 (diff) | |
| download | firmware-d40d18ab1ae8a1ef9feb408e43d4b840d37998a8.tar.gz firmware-d40d18ab1ae8a1ef9feb408e43d4b840d37998a8.tar.bz2 firmware-d40d18ab1ae8a1ef9feb408e43d4b840d37998a8.zip | |
don't believe the hex files are posted to qmk.fm
| -rw-r--r-- | readme.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -97,7 +97,7 @@ In every keymap folder, the following files are recommended: The `make` command is how you compile the firmware into a .hex file, which can be loaded by a dfu programmer (like dfu-progammer via `make dfu`) or the [Teensy loader](https://www.pjrc.com/teensy/loader.html) (only used with Teensys). You can run `make` from the root (`/`), your keyboard folder (`/keyboards/<keyboard>/`), or your keymap folder (`/keyboards/<keyboard>/keymaps/<keymap>/`) if you have a `Makefile` there (see the example [here](/doc/keymap_makefile_example.mk)). -By default, this will generate a `<keyboard>_<keymap>.hex` file in whichever folder you run `make` from. These files are ignored by git, so don't worry about deleting them when committing/creating pull requests. Your .hex file will also be available on qmk.fm/keyboards/<keyboard>/keymaps/<keymap>/. +By default, this will generate a `<keyboard>_<keymap>.hex` file in whichever folder you run `make` from. These files are ignored by git, so don't worry about deleting them when committing/creating pull requests. Below are some definitions that will be useful: |