TheArchive/mayhem-firmware
1
0
Fork 0
mirror of https://github.com/portapack-mayhem/mayhem-firmware.git synced 2024-11-27 12:05:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Compile firmware (markdown)

E.T 2024-01-22 11:33:40 +01:00
parent d48cabaccd
commit 669d2f3a86
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Compile-firmware.md

@ -78,13 +78,23 @@ git clone https://github.com/eried/portapack-mayhem.git
cd portapack-mayhem cd portapack-mayhem
git submodule update --init --recursive git submodule update --init --recursive
``` ```
* For building: * For building the docker image:
`docker build -t portapackccache -f dockerfile-nogit .` `docker build -t portapackccache -f dockerfile-nogit .`
* For running (in the root of the repo): * For running the image to build firmware (in the root of the repo):
`docker run -it -v ${PWD}:/havoc portapackccache` `docker run -it --rm -v ${PWD}:/havoc portapackccache` \
This runs and then immediatelly deletes the container, so that they arent pile up in your docker instance.
Remember that you have to create a `build` folder before running the image. * You can specify the number of jobs to run in parallel during compilation.
To speed up the build specify the number of cores available: ```docker run -it --rm -v ${PWD}:/havoc portapackccache -j4```
* Alternatively if you want to have a single persistent container, and just execute it when necessary
* Create the persistent container (it will also build the firmware once): ```docker run --name portapackbuild -it -v ${PWD}:/havoc portapackccache -j4```
* Run the existing container: ```docker start portapackbuild```
_You no longer have to create a `build` folder before running the image._
# Using Buddy.Works (and other CI platforms) # Using Buddy.Works (and other CI platforms)