Hey folks,
I've now got 3 or 4 different types of devices (and with the ipq806x / ipq807x split, three architectures) I'm managing builds for, and I'm wondering one of you has a nice system to manage all the metadata for those builds.
I've already stolen what I currently use from one of you (apologies, I forget where I even stole it from now!), but thought I'd see if there's a better way to manage multiple builds for multiple architectures.
My goals are generally to provide near-stock builds for bugfixes and backports for hardware I own and am interested in hacking on -- currently ipq806x and ipq807x (but also ipq40xx because some folks asked for backports for other Meraki hardware I didn't have but which seemed trivial to produce).
This all works great for the occasional GitHub CI build on one of the maintained OpenWRT branches[*] but it becomes a bit of a PITA when I cut a new experimental branch (gotta copy all those scripts), or when I do want to do produce a local build, where I'm not sure the way I'm generating .config files is sane .
Here are my current (stolen) build scripts -- it's really just some GitHub workflows and a .config generation script: https://github.com/rkboni/openwrt/commit/df02bec3da53eea41f54f025e5a5653c23504b59
Anyone have better suggestions for managing the metadata for multiple targets on multiple architectures and making it easy to share between GitHub CI builds and local builds?
Thanks!
[*] I am eternally thankful for this... so nice to be able to put GitHub's CPUs to work for me and even better not requiring a local dev env, or having to solve issues of how to build on an ARM MAC, or ...