Allan Wind
b3753fd711
The target all was previous running setup followed by build. As both setup and build are phony targets they run in sequence and because the firmware contain the timestamp they always run (dependencies doesn't do anything). all now does exactly what it says on the tin without introducing non-standard targets. clean now removes the images that created during build which is what you expect from that target. See: https://www.gnu.org/software/make/manual/html_node/Standard-Targets.html#Standard-Targets
ADV360-PRO-ZMK
To build Firmware in GitHub Actions
Setup
- Fork this repo.
- Enable GitHub Actions on your fork.
Build firmware
- Push a commit to trigger the build.
- Download the artifact.
To build Firmware locally using a container
First run
Note: Either Podman or Docker is required, Podman is preferred if both are present.
- Execute
make all. - Check the
firmwaredirectory for the latest firmware build.
Subsequent runs
If the only file you have changed is config/adv360.keymap, execute make build and check the firmware directory for the latest firmware build.
If you have changed other files in the config directory (such as config/west.yml) you will need to execute make all to rebuild the Docker image as well as the firmware.
Flash firmware
Resources can be found on Kinesis.com https://kinesis-ergo.com/support/kb360pro/#firmware-updates https://kinesis-ergo.com/support/kb360pro/#manuals