diff options
author | Leah Rowe <leah@libreboot.org> | 2024-12-02 20:37:26 +0000 |
---|---|---|
committer | Leah Rowe <leah@libreboot.org> | 2024-12-02 20:41:05 +0000 |
commit | 5b4c9158e5a79f8d7e776c8c4ece69dda5aa8690 (patch) | |
tree | 76906ab132b97d962177c479e4994b0fe8b92bfd /resources/grub/patches | |
parent | b95a411a3645b72036101aaa8f8ad28758eefd15 (diff) |
trees: Allow using a custom clean command
On coreboot for example, as Mate has told me, if you're
making Kconfig changes and re-compiling, sometimes the
actual image that you build might still have the old one
in it, due to how coreboot's build system works.
To mitigate this, you can just always run distclean before
doing the build, but lbmk was doing just clean.
In practise, we did not find any issues, but this change should
be harmless, and might prevent such issues in the future. It's
even possible that we might have already encountered this before
and not realised, and we were just lucky that no noticeable issues
were caused.
It's *also* possible that the reverse is true: an issue that
was previously covered up, then that issue will now be exposed.
However, if that turns out to be true, then that is good because
we are exposing said bugs and then we will know to fix them!
Anyway, the variable in target.cfg is:
cleancmd="whatever_you_want"
e.g.
cleancmd="distclean"
You may also specify this in global mkhelper.cfg files, per
project; I've already done this for SeaBIOS, coreboot
and U-Boot, since all of these use Kconfig files.
Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'resources/grub/patches')
0 files changed, 0 insertions, 0 deletions