Our firmware build system is orchestrated by firmware/Makefile. While this works, it is an improper use of Makefile since we using it to run commands in sequence rather than compile targets from prerequisites (which we delegate to CMake).
I came across Task https://taskfile.dev/ which claims to be an alternative and may be a more appropriate tool.
Your task is to:
Write firmware/Taskfile.dist.yml to replicate the functionality of our Makefile. The command line interface does not need to be exactly the same but the user should be able to specify the action (build / st-flash / config / clean), project and platform.
Our firmware build system is orchestrated by
firmware/Makefile
. While this works, it is an improper use of Makefile since we using it to run commands in sequence rather than compile targets from prerequisites (which we delegate to CMake).I came across Task https://taskfile.dev/ which claims to be an alternative and may be a more appropriate tool.
Your task is to:
Write
firmware/Taskfile.dist.yml
to replicate the functionality of our Makefile. The command line interface does not need to be exactly the same but the user should be able to specify the action (build / st-flash / config / clean), project and platform.In your PR, write your observations about Task vs Make.
Add installation instructions to
docs/docs/firmware/dev-setup.md
. See instruction for adding docs