aboutsummaryrefslogtreecommitdiffstats
path: root/docker/build.sh
Commit message (Collapse)AuthorAgeFilesLines
* docker: fix NRF_SDK download and subsequent build.sh (#2299)NeroBurner2025-05-271-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The upstream NRF-SDK download url and zip archive filename changed, which was fixed with https://github.com/InfiniTimeOrg/InfiniTime/pull/2270 But the archive contents stayed the same, with the "old" folder name. After #2270 we have basically the same docker-container as before the PR, but the `GetNrfSdk` function of the `build.sh` script is called again during firmware build time as the expected foldername for the SDK isn't the same as the zip filename: ```sh [ ! -d "$TOOLS_DIR/$NRF_SDK_VER" ] && GetNrfSdk ``` Then during the build the `buils.sh` script tries to execute `GetNrfSdk` again, which fails as the files already exist resulting in the following error: ``` replace /opt/nRF5_SDK_15.3.0_59ac345/components/802_15_4/api/HAL/hal_atomic.h? [y]es, [n]o, [A]ll, [N]one, [r]ename: NULL ``` Fix this by reverting the `NRF_SDK_VER` to the folder name in the zip archive and by some character replacement generate the download URL from the above (the download is in lower-case without the `_` and `.` characters). Furthermore add safeguards to check after the `GetNrfSdk` call if the expected folder is really created. Then we have an error early during container image creation if the contents of the zip-archive are unexpected.
* Fix nRF SDK download links (#2270)Darius Arnold2025-05-211-2/+2
| | | nRF has moved the download to a new location- Update the build script to fetch from the same URL the download website currently provides.
* docker: Make build.sh more portableRiku Isokoski2023-01-071-9/+9
|
* Revert "enable CMake unity build in build.sh"Riku Isokoski2022-12-311-1/+0
| | | | This reverts commit 35654fbd982e27383ffc15446d9ab0a8606ae29d.
* Revert "Update docker/build.sh"Riku Isokoski2022-12-311-1/+1
| | | | This reverts commit 7103f9d8063431b778df83244de5862d963e1ce8.
* Update docker/build.shDominik Nussbaumer2022-12-271-1/+1
| | | Co-authored-by: NeroBurner <pyro4hell@gmail.com>
* enable CMake unity build in build.shtnixeu2022-12-271-0/+1
|
* fixing build.sh not returning error in build (#1460)cybuzuma2022-12-131-1/+11
| | | | | | | | | | Return the build status as return code from the `main` helper function. In the process convert the handling if the file was sourced or directly executed into an explicit if/else statement to make the intent clearer. In case of an build error the error is now reported at the build step, where the error happened. Fixes: https://github.com/InfiniTimeOrg/InfiniTime/issues/1292
* Remove CMake targets and corresponding CLI arguments that are specific to ↵Jean-François Milants2022-09-171-1/+0
| | | | the debugging environment (USE_JLINK, USE_OPENOCD and USE_GDB_CLIENT).
* Small improvement in generate-fonts.py following code review.Jean-François Milants2022-09-111-1/+6
| | | | Add lv_img_conf in Docker image to build resources at build time.
* Downgrade GNU Arm Toolchain to 10.3-2021.10Finlay Davidson2022-07-081-3/+3
| | | | | | This is because of this bug: https://community.arm.com/support-forums/f/compilers-and-libraries-forum/52623/gcc-11-2-arm-none-eabi-internal-compiler-error-illegal-instruction It is causing some of the GitHub Actions builds to fail.
* Update arm gcc toolchain to 11.2-2022.02Finlay Davidson2022-06-111-6/+7
| | | | | | Updates the buildAndProgram doc and the docker image, which means GitHub Actions will also use the new toolchain.
* The main build workflow for GitHub Actions now uses the infinitime-build ↵Jean-François Milants2022-05-261-10/+6
| | | | | | docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format. The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
* Update git URLS, MCUboot is now independent w/ different GitHub org.carlosperate2021-10-171-1/+1
|
* Add new cmake option to disable the generation of DFU file (which needs ↵Jean-François Milants2021-02-011-0/+1
| | | | adafruit-nrfutil on the build machine) : BUILD_DFU (disabled by default, enabled in docker build).
* check for cmake build-success before running post-build.shpetter2021-01-231-3/+5
|
* Make TOOLS_DIR if neededJoe Eaves2020-12-221-0/+3
| | | | Added some extra dir names to gitignore
* Integrate improvements from #137Joe Eaves2020-12-211-2/+2
| | | | Also fixed a bug with empty quoted strings
* Unify the Dockerfiles by fleshing out build.shJoe Eaves2020-12-211-6/+67
| | | | Script is written to handle it's own dependencies so it can be used within Docker or on the host system
* Docker build : split build.sh into 2 scripts : build.sh that always exists ↵JF2020-08-201-0/+12
| | | | and post_build.sh that is generated by cmake build.sh
* All output files (bin, hex, image, dfu) contain the version of the project ↵JF2020-08-191-25/+0
| | | | | | | in their filename. Update Docker build script accordingly. Also fix permission issue with docker build (all files belonged to root).
* Add docker file create docker image that builds the project on amd64 and ↵JF2020-08-191-0/+25
arm64 arch.