|
1 | 1 | # Build the project using Docker |
2 | | -A [Docker image (Dockerfile)](../docker) containing all the build environment is available for X86_64 and AMD64 architectures. This image makes the build of the firmware and the generation of the DFU file for OTA. |
3 | 2 |
|
4 | | -## Build the image |
5 | | -The image is not (yet) available on DockerHub, you need to build it yourself, which is quite easy. The following commands must be run from the root of the project. |
| 3 | +A [Docker image (Dockerfile)](../docker) containing all the build environment is available for X86_64 and AMD64 architectures. These images make the build of the firmware and the generation of the DFU file for OTA quite easy, as well as preventing clashes with any other toolchains or development environments you may have installed. |
| 4 | + |
| 5 | +Based on Ubuntu 18.04 with the following build dependencies: |
| 6 | + |
| 7 | +* ARM GCC Toolchain |
| 8 | +* nRF SDK |
| 9 | +* MCUBoot |
| 10 | +* adafruit-nrfutil |
| 11 | + |
| 12 | +## Run a container to build the project |
| 13 | + |
| 14 | +The `infinitime-build` image contains all the dependencies you need. The default `CMD` will compile sources found in `/sources`, so you need only mount your code. |
| 15 | + |
| 16 | +This example will build the firmware, generate the MCUBoot image and generate the DFU file. Outputs will be written to **<project_root>/build/output **: |
6 | 17 |
|
7 | | -If you are running on a x86_64 computer : |
| 18 | +```bash |
| 19 | +cd <project_root> # e.g. cd ./work/Pinetime |
| 20 | +docker run --rm -it -v $(pwd):/sources infinitime-build |
8 | 21 | ``` |
9 | | -docker image build -t infinitime-build --build-arg USER_ID=$(id -u) --build-arg GROUP_ID=$(id -g) docker/x86_64/ |
| 22 | + |
| 23 | +If you only want to build a single CMake target, you can pass it in as the first parameter to the build script. This means calling the script explicitly as it will override the `CMD`. Here's an example For `pinetime-app`: |
| 24 | + |
| 25 | +```bash |
| 26 | +docker run --rm -it -v $(pwd):/sources infinitime-build /opt/build.sh pinetime-app |
10 | 27 | ``` |
11 | 28 |
|
12 | | -And if your are running on an ARM64 device (tested on RaspberryPi4 and Pine64 PineBookPro): |
| 29 | +The image is built using 1000:1000 for the user id and group id. If this is different to your user or group ids (run `id -u` and `id -g` to find out what your id values are if you are unsure), you will need to override them via the `--user` parameter in order to prevent permission errors with the output files (and the cmake build cache). |
| 30 | + |
| 31 | +Running with this image is the same as above, you just specify the ids to `docker run` |
| 32 | + |
| 33 | +```bash |
| 34 | +docker run --rm -it -v $(pwd):/sources --user $(id -u):$(id -g) pfeerick/infinitime-build |
13 | 35 | ``` |
14 | | -docker image build -t infinitime-build --build-arg USER_ID=$(id -u) --build-arg GROUP_ID=$(id -g) docker/arm64/ |
| 36 | + |
| 37 | +Or you can specify your user id and group id (by number, not by name) directly: |
| 38 | + |
| 39 | +```bash |
| 40 | +docker run --rm -it -v $(pwd):/sources --user 1234:1234 infinitime-build |
15 | 41 | ``` |
16 | 42 |
|
17 | | -This operation will take some time. It builds a Docker image based on Ubuntu, install some packages, download the ARM toolchain, the NRF SDK, MCUBoot and adafruit-nrfutil. |
| 43 | +## Using the image from Docker Hub |
18 | 44 |
|
19 | | -When this is done, a new image named *infinitime-build* is available. |
| 45 | +The image is avaiable via Docker Hub for both the amd64 and arm64v8 architectures at [pfeerick/infinitime-build](https://hub.docker.com/repository/docker/pfeerick/infinitime-build). |
20 | 46 |
|
21 | | -## Run a container to build the project: |
| 47 | +It can be pulled (downloaded) using the following command: |
22 | 48 |
|
23 | | -``` |
24 | | -docker run --rm -v <project_root>:/sources infinitime-build |
| 49 | +```bash |
| 50 | +docker pull pfeerick/infinitime-build |
25 | 51 | ``` |
26 | 52 |
|
27 | | -Replace *<project_root>* by the path of the root of the project on your computer. For example: |
| 53 | +The default `latest` tag *should* automatically identify the correct image architecture, but if for some reason Docker does not, you can specify it manually: |
28 | 54 |
|
29 | | -``` |
30 | | -docker run --rm -v /home/jf/git/PineTime:/sources infinitime-build |
| 55 | +* For AMD64 (x86_64) systems: `docker pull pfeerick/infinitime-build:amd64` |
| 56 | + |
| 57 | +* For ARM64v8 (ARM64/aarch64) systems: `docker pull pfeerick/infinitime-build:arm64v8` |
| 58 | + |
| 59 | +## Build the image |
| 60 | + |
| 61 | +You can build the image yourself if you like! |
| 62 | + |
| 63 | +The following commands must be run from the root of the project. This operation will take some time but, when done, a new image named *infinitime-build* is available. |
| 64 | + |
| 65 | +```bash |
| 66 | +docker image build -t infinitime-build ./docker |
31 | 67 | ``` |
32 | 68 |
|
33 | | -This will start a container, build the firmware and generate the MCUBoot image and the DFU file. The output of the build is stored in **<project_root>/built/output **. |
| 69 | +The `PUID` and `PGID` build arguments are used to set the user and group ids used in the container, meaning you will not need to specify it later unless they change for some reason. Specifying them is not mandatory, as this can be over-ridden at build time via the `--user` flag, but doing so will make the command you need to run later a bit shorter. In the below examples, they are set to your current user id and group id automatically. You can specify them manually, but they must be specified by number, not by name. |
| 70 | + |
| 71 | +```bash |
| 72 | +docker image build -t infinitime-build --build-arg PUID=$(id -u) --build-arg PGID=$(id -g) ./docker |
| 73 | +``` |
0 commit comments