Hi Rasmus, On Wed, Jan 25, 2023 at 11:59 AM Rasmus Villemoes <rasmus.villem...@prevas.dk> wrote:
> So I also got curious about that part, because when I build > tools-only_defconfig with older U-Boot releases I don't get a bmp_logo > tool built. > > I think I figured that out (but only after it's been revealed that this > was about Fedora's packaging of u-boot-tools). Fedora seems to do > > %make_build HOSTCC="gcc $RPM_OPT_FLAGS" CROSS_COMPILE="" > tools-only_defconfig O=builds/ > > %make_build HOSTCC="gcc $RPM_OPT_FLAGS" CROSS_COMPILE="" tools-all O=builds/ > > so unlike the Yocto case, the build target is tools-all and not > cross_tools. Hence the top Makefile sets HOST_TOOLS_ALL=y, which in > tools/Makefile then hits > > ifneq ($(HOST_TOOLS_ALL),) > CONFIG_ARCH_KIRKWOOD = y > ... > endif > > and that block used to, until 1dc6517649f2, contain > > CONFIG_LCD_LOGO = y > > with the corresponding > > hostprogs-$(CONFIG_LCD_LOGO) += bmp_logo > > further down. > > IOW, it wasn't really tools-only_defconfig per se that used to cause > bmp_logo to get built, it was the tools-all target. Thanks for the in-depth investigation, appreciated it.
