At present it is not actually possible to discover the defconfig file that
was used to build U-Boot, so far as I can tell. Write this out to a file
in the build directory, so this is visible.
Signed-off-by: Simon Glass <s...@chromium.org>
---
scripts/kconfig/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/kconfig/Makefile b/scripts/kconfig/Makefile
index d52128425ce..bfb92a50bf9 100644
--- a/scripts/kconfig/Makefile
+++ b/scripts/kconfig/Makefile
@@ -92,8 +92,10 @@ else
endif
endif
+# Write out the defconfig name to a file so we know which board was configured
%_defconfig: $(obj)/conf
$(Q)$< $(silent) --defconfig=arch/$(SRCARCH)/configs/$@ $(Kconfig)
+ $(Q)echo $(subst _defconfig,,$@) > .defconfig_name
# Added for U-Boot (backward compatibility)
%_config: %_defconfig
--
2.32.0.605.g8dce9f2422-goog
