From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] Makefile: export BR2_CONFIG_FILE, pointing to our .config
Date: Tue, 08 Jan 2013 07:50:51 +0100 [thread overview]
Message-ID: <50EBC1CB.8030900@mind.be> (raw)
In-Reply-To: <fd01d05b62a384b43722e790e3e491f87c818797.1357595083.git.yann.morin.1998@free.fr>
Hi Yann,
On 07/01/13 22:52, Yann E. MORIN wrote:
> Support scripts (in support/) may need to parse the .config file,
> so give them an easy access to it, by exporting CONFIG_FILE with
> the fully-qualified path to .config.
Good idea!
>
> Signed-off-by: "Yann E. MORIN"<yann.morin.1998@free.fr>
> ---
> Makefile | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 4b09437..7a2902d 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -91,6 +91,10 @@ EXTRAMAKEARGS = O=$(O)
> NEED_WRAPPER=y
> endif
>
> +# Scripts in support/ may need to parse out .config, so give
> +# them easy access
> +export BR2_CONFIG_FILE=$(CONFIG_DIR)/.config.
Convention is that BR2_* is set by Kconfig. I kind of like that, it
helps us developers to understand a variable's meaning.
[Yes, BR2_DEFCONFIG which I introduced myself is an exception. However,
I have a pending patch that moves it into the .config :-)]
> +
> # Pull in the user's configuration file
> ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
> -include $(CONFIG_DIR)/.config
I would replace the occurences of the plain config file with
$(CONFIG_FILE). $(CONFIG_FILE).nopkg does indeed look stupid, so that one
should be left alone.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-01-08 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 21:52 [Buildroot] [pull request] Pull request for branch yem-misc-fixes Yann E. MORIN
2013-01-07 21:52 ` [Buildroot] [PATCH 1/3] Makefile: export BR2_CONFIG_FILE, pointing to our .config Yann E. MORIN
2013-01-07 22:10 ` Yann E. MORIN
2013-01-08 6:50 ` Arnout Vandecappelle [this message]
2013-01-08 12:51 ` Yann E. MORIN
2013-01-08 13:07 ` Arnout Vandecappelle
2013-01-08 13:46 ` Yann E. MORIN
2013-01-08 14:27 ` Arnout Vandecappelle
2013-01-13 20:45 ` Peter Korsgaard
2013-01-13 21:34 ` Yann E. MORIN
2013-01-07 21:52 ` [Buildroot] [PATCH 2/3] support/dependencies: use globally-exported BR2_CONFIG_FILE Yann E. MORIN
2013-01-07 21:52 ` [Buildroot] [PATCH 3/3] toolchain/crostool-ng: use globally-exported CONFIG_FILE Yann E. MORIN
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=50EBC1CB.8030900@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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