From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] build: add 'file' option for 'make defconfig'
Date: Sat, 11 Feb 2012 17:01:27 +0100 [thread overview]
Message-ID: <201202111701.27270.arnout@mind.be> (raw)
In-Reply-To: <1328918596-19369-1-git-send-email-felipe.contreras@gmail.com>
On Saturday 11 February 2012 01:03:16 Felipe Contreras wrote:
> So that this works:
>
> % make defconfig file=~/busybox-defconfig
>
> Right now we have to do:
>
> % make $PWD/output/build/buildroot-config/conf
> % $PWD/output/build/buildroot-config/conf --defconfig=~/busybox-defconfig Config.in
>
> And the first command would through an error. Not nice.
+1! And such a graceful solution too!
One remark, though: we normally use capitals for variables. Also I'd make
it more clear that the file means the defconfig file, so you can write:
make DEFCONFIG=~/my-buildroot.config defconfig world
And eventually we can even update the non-BR2_HAVE_DOT_CONFIG targets to
default to defconfig if DEFCONFIG is defined.
Note that the way to do it without this patch would be:
cp ~/busybox-defconfig configs/busybox_defconfig
make busybox_defconfig
which doesn't error out. However, it does require a writable buildroot
directory and it makes it dirty.
Oh and another thing, I guess the example should by 'buildroot-defconfig'.
Regards,
Arnout
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
> Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 25da853..5a26961 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -594,7 +594,7 @@ silentoldconfig: $(BUILD_DIR)/buildroot-config/conf outputmakefile
>
> defconfig: $(BUILD_DIR)/buildroot-config/conf outputmakefile
> @mkdir -p $(BUILD_DIR)/buildroot-config
> - @$(COMMON_CONFIG_ENV) $< --defconfig $(CONFIG_CONFIG_IN)
> + @$(COMMON_CONFIG_ENV) $< --defconfig$(addprefix =,$(file)) $(CONFIG_CONFIG_IN)
>
> %_defconfig: $(BUILD_DIR)/buildroot-config/conf $(TOPDIR)/configs/%_defconfig outputmakefile
> @mkdir -p $(BUILD_DIR)/buildroot-config
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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:[~2012-02-11 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 0:03 [Buildroot] [PATCH] build: add 'file' option for 'make defconfig' Felipe Contreras
2012-02-11 16:01 ` Arnout Vandecappelle [this message]
2012-02-11 17:29 ` Felipe Contreras
2012-02-14 9:46 ` Thomas De Schampheleire
2012-02-14 12:44 ` Felipe Contreras
2012-02-14 13:53 ` Arnout Vandecappelle
2012-02-14 16:15 ` Felipe Contreras
2012-02-15 6:58 ` Thomas De Schampheleire
2012-02-15 11:53 ` Felipe Contreras
2012-02-15 11:54 ` Thomas De Schampheleire
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=201202111701.27270.arnout@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