commit
2bed835a33
|
@ -0,0 +1,28 @@
|
||||||
|
FROM debian:jessie
|
||||||
|
MAINTAINER Erik Dasque <erik@frenchguys.com>
|
||||||
|
|
||||||
|
RUN apt-get update
|
||||||
|
RUN apt-get install --no-install-recommends -y build-essential \
|
||||||
|
gcc \
|
||||||
|
unzip \
|
||||||
|
wget \
|
||||||
|
zip \
|
||||||
|
gcc-avr \
|
||||||
|
binutils-avr \
|
||||||
|
avr-libc \
|
||||||
|
dfu-programmer \
|
||||||
|
dfu-util \
|
||||||
|
gcc-arm-none-eabi \
|
||||||
|
binutils-arm-none-eabi \
|
||||||
|
libnewlib-arm-none-eabi \
|
||||||
|
git
|
||||||
|
|
||||||
|
RUN apt-get clean
|
||||||
|
RUN rm -rf /var/lib/apt/lists/*
|
||||||
|
|
||||||
|
ENV keyboard=ergodox_ez
|
||||||
|
ENV keymap=default
|
||||||
|
|
||||||
|
VOLUME /qmk
|
||||||
|
WORKDIR /qmk
|
||||||
|
CMD make clean ; make keyboard=${keyboard} keymap=${keymap}
|
15
readme.md
15
readme.md
|
@ -75,6 +75,21 @@ Debian/Ubuntu example:
|
||||||
sudo apt-get update
|
sudo apt-get update
|
||||||
sudo apt-get install gcc-avr avr-libc dfu-programmer
|
sudo apt-get install gcc-avr avr-libc dfu-programmer
|
||||||
|
|
||||||
|
### Docker
|
||||||
|
|
||||||
|
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:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# You'll run this every time you want to build a keymap
|
||||||
|
# modify the keymap and keyboard assigment to compile what you want
|
||||||
|
# defaults are ergodox_ez/default
|
||||||
|
|
||||||
|
docker run -e keymap=gwen -e keyboard=ergodox_ez --rm -v $('pwd'):/qmk:rw edasque/qmk_firmware
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
This will compile the targetted keyboard/keymap and leave it in your QMK directory for you to flash.
|
||||||
|
|
||||||
### Vagrant
|
### Vagrant
|
||||||
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).
|
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).
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue