Attention is currently required from: Martin L Roth, Elyes Haouas.
Martin Roth has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/68956 )
Change subject: util/scripts: Add script to run abuild on specific SOCs ......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
I don't know if it is possible or not (and maybe this an other story), but it'd be great if we can s […]
It already accepts an option - I just hadn't written up the help yet.
Just run it as `testsoc SOC_AMD_CEZANNE` and it will build all of the boards using that chip.
Maybe I'll change the name to test_brds or something, because really you can put any config option into the command line and it will search for mainboard directories that contain that Kconfig option as either a select or config. So `testsoc MAINBOARD_HAS_CHROMEOS` would build all of the chromeos boards.
I can't directly add a way to check which boards are affected by a patch, because we actually need to build the board to find that out.
I'm working on my rm_unused_code tool right now though, and as part of that, I can get a list of files used by each board & build. So by making a list of boards that use each file, we could look up which boards use files affected by a change and build those. That'll take a bit of time, but it's definitely doable.
So it's possible that a board wouldn't actually be affected by a patch because an option used in the patch is disabled or something like that, but it would at least give us better granularity than we have now.
We'll also want to update abuild to take config file, because the current method of just calling abuild with each board is much less efficient than abuild's current full build.
I'll go ahead and clean up the script, add a help, command line parsing and some additional options.