diff options
| author | Jack Humbert <jack.humb@gmail.com> | 2016-07-21 20:58:39 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-07-21 20:58:39 -0400 |
| commit | 2bed835a331101c1ad70e97f8ce40bd85f546949 (patch) | |
| tree | a43258e083941262134a10459d6901c0d32ddce6 /readme.md | |
| parent | fc9f12864859dffe7a50dd509013ec916d338fd8 (diff) | |
| parent | aa2a79bbfa5e5134fc83daf5732ca4774edf2dc2 (diff) | |
| download | qmk_firmware-2bed835a331101c1ad70e97f8ce40bd85f546949.tar.gz qmk_firmware-2bed835a331101c1ad70e97f8ce40bd85f546949.zip | |
Merge pull request #525 from edasque/master
Added Docker as a simple way to build firmwares
Diffstat (limited to 'readme.md')
| -rw-r--r-- | readme.md | 15 |
1 files changed, 15 insertions, 0 deletions
| @@ -75,6 +75,21 @@ Debian/Ubuntu example: | |||
| 75 | sudo apt-get update | 75 | sudo apt-get update |
| 76 | sudo apt-get install gcc-avr avr-libc dfu-programmer | 76 | sudo apt-get install gcc-avr avr-libc dfu-programmer |
| 77 | 77 | ||
| 78 | ### Docker | ||
| 79 | |||
| 80 | If this is a bit complex for you, Docker might be the turn-key solution you need. After installing [Docker](https://www.docker.com/products/docker), run the following command at the root of the QMK folder to build a keyboard/keymap: | ||
| 81 | |||
| 82 | ```bash | ||
| 83 | # You'll run this every time you want to build a keymap | ||
| 84 | # modify the keymap and keyboard assigment to compile what you want | ||
| 85 | # defaults are ergodox_ez/default | ||
| 86 | |||
| 87 | docker run -e keymap=gwen -e keyboard=ergodox_ez --rm -v $('pwd'):/qmk:rw edasque/qmk_firmware | ||
| 88 | |||
| 89 | ``` | ||
| 90 | |||
| 91 | This will compile the targetted keyboard/keymap and leave it in your QMK directory for you to flash. | ||
| 92 | |||
| 78 | ### Vagrant | 93 | ### Vagrant |
| 79 | If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](VAGRANT_GUIDE.md). | 94 | If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](VAGRANT_GUIDE.md). |
| 80 | 95 | ||
