mirror of
https://codeberg.org/libreboot/lbmk.git
synced 2026-07-11 05:52:36 +02:00
Leah Rowe
5b4c9158e5
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>
19 lines
569 B
INI
19 lines
569 B
INI
. "include/rom.sh"
|
|
|
|
makeargs="UPDATED_SUBMODULES=1 CPUS=$XBMK_THREADS"
|
|
build_depend="seabios/default grub/default memtest86plus u-boot/amd64coreboot"
|
|
cleancmd="distclean"
|
|
|
|
seavgabiosrom="elf/seabios/default/libgfxinit/vgabios.bin"
|
|
|
|
pv="payload_uboot payload_seabios payload_memtest payload_grub"
|
|
pv="$pv payload_uboot_i386 payload_uboot_amd64"
|
|
v="initmode ubootelf grub_scan_disk uboot_config grubtree grubelf pname"
|
|
v="$v displaymode tmprom newrom"
|
|
eval `setvars "n" $pv`
|
|
eval `setvars "" $v`
|
|
|
|
premake="mkvendorfiles"
|
|
mkhelper="mkcorebootbin"
|
|
postmake="mkcoreboottar"
|