From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Michal Simek <monstr@monstr.eu>,
huang lin <hl@rock-chips.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Kever Yang <kever.yang@rock-chips.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Wolfgang Denk <wd@denx.de>
Subject: [PATCH v2 1/2] Makefile: Create a file to indicate the config
Date: Sun, 30 Jan 2022 08:52:24 -0700 [thread overview]
Message-ID: <20220130155225.726890-1-sjg@chromium.org> (raw)
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 <sjg@chromium.org>
---
(no changes since v1)
scripts/kconfig/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/kconfig/Makefile b/scripts/kconfig/Makefile
index 12e525ee31f..83a40c7eb3b 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.35.0.rc2.247.g8bbb082509-goog
next reply other threads:[~2022-01-30 15:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 15:52 Simon Glass [this message]
2022-01-30 15:52 ` [PATCH v2 2/2] Makefile: Don't allow new boards with SPL_FIT_GENERATOR Simon Glass
2022-01-30 19:40 ` Michal Simek
2022-01-30 23:14 ` Simon Glass
2022-01-31 14:24 ` Tom Rini
2022-01-31 16:13 ` Simon Glass
2022-01-31 16:15 ` Tom Rini
2022-01-31 17:27 ` Simon Glass
2022-01-31 18:00 ` Tom Rini
2022-01-31 19:57 ` Simon Glass
2022-01-31 20:40 ` Tom Rini
2022-01-31 21:22 ` Simon Glass
2022-01-31 22:05 ` Tom Rini
2022-01-31 22:59 ` Simon Glass
2022-01-31 23:25 ` Tom Rini
2022-01-31 23:32 ` Tom Rini
2022-02-01 14:05 ` Simon Glass
2022-02-01 15:42 ` Simon Glass
2022-02-01 16:08 ` Mark Kettenis
2022-02-01 16:24 ` Simon Glass
2022-01-31 22:02 ` Mark Kettenis
2022-01-31 14:24 ` [PATCH v2 1/2] Makefile: Create a file to indicate the config Tom Rini
2022-01-31 16:13 ` Simon Glass
2022-01-31 16:21 ` Tom Rini
2022-01-31 17:27 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220130155225.726890-1-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=monstr@monstr.eu \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=wd@denx.de \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox