On Wed, Jul 19, 2023 at 09:26:01PM +0800, Zhangjin Wu wrote: > To avoid run targets one by one manually and boringly, let's string them > with IMAGE and .config, the MAKE command will trigger the dependencies > for us. > > Note, to allow do menuconfig before extconfig manually, only trigger > defconfig while the .config is not there, it means only trigger > defconfig for the first run or after a mrproper. > > Signed-off-by: Zhangjin Wu <falcon@xxxxxxxxxxx> > --- > tools/testing/selftests/nolibc/Makefile | 18 +++++++++++++----- > 1 file changed, 13 insertions(+), 5 deletions(-) > > diff --git a/tools/testing/selftests/nolibc/Makefile b/tools/testing/selftests/nolibc/Makefile > index 83cb4b017bef..541f3565e584 100644 > --- a/tools/testing/selftests/nolibc/Makefile > +++ b/tools/testing/selftests/nolibc/Makefile (...) > -extconfig: > +extconfig: $(KERNEL_CONFIG) > $(Q)$(srctree)/scripts/kconfig/merge_config.sh -O "$(objtree)" -m "$(KERNEL_CONFIG)" $(foreach c,$(EXTCONFIG),$(wildcard $(CURDIR)/configs/$c)) > $(Q)$(MAKE_KERNEL) KCONFIG_ALLCONFIG="$(KERNEL_CONFIG)" allnoconfig > > -kernel: initramfs > +kernel: extconfig > + $(Q)$(MAKE) --no-print-directory initramfs There seems to be something wrong here. From what I'm seeing, now if I run "make kernel" it will run extconfig and possibly change the config I just edited. Or am I missing something ? I must confess all of this is becoming more and more obscure :-( Willy
