From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/6] Add documentation for merged defconfigs
Date: Tue, 5 Jul 2016 08:16:44 +0200 [thread overview]
Message-ID: <20160705081644.6fd47292@free-electrons.com> (raw)
In-Reply-To: <20160705060625.GB27663@tungsten.ozlabs.ibm.com>
Hello Sam,
On Tue, 5 Jul 2016 16:06:25 +1000, Sam Bobroff wrote:
> > Instead we recommend to use merge_config.sh from outside of Buildroot to
> > generate the merged defconfig before calling make. Maybe we should add some
> > documentation in the manual to explain how to use it.
>
> That seems fine, it might even be possible to add something to
> $(BR2_EXTERNAL)/external.mk to hook it directly into the Makefiles.
>
> Could you elaborate a bit on what you mean by using merge_config.sh outside of
> buildroot? Would the fragment files still be checked into buildroot somewhere
> (but just not hooked into the build system) or would they be maintained outside
> it?
The idea is that Buildroot just takes as input a configuration file.
How this configuration file is provided/generated is not Buildroot's
responsibility.
For example, you could have in your BR2_EXTERNAL tree a bunch of
defconfig fragments, and then a "genconfig" shell script to generate the
final configuration you want to build using the defconfig fragments.
This "genconfig" script relies on merge_config.sh to actually merge the
relevant fragments together.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-05 6:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 5:06 [Buildroot] [PATCH v3 0/6] Makefile: Support merged and nested defconfigs Sam Bobroff
2016-06-29 5:06 ` [Buildroot] [PATCH v3 1/6] Add support for merged defconfigs Sam Bobroff
2016-07-01 8:47 ` Romain Naour
2016-07-05 5:44 ` Sam Bobroff
2016-06-29 5:06 ` [Buildroot] [PATCH v3 2/6] Add documentation " Sam Bobroff
2016-07-01 13:18 ` Romain Naour
2016-07-05 6:06 ` Sam Bobroff
2016-07-05 6:16 ` Thomas Petazzoni [this message]
2016-07-06 3:35 ` Sam Bobroff
2016-07-05 19:32 ` Patrick Williams
2016-07-05 22:13 ` Samuel Mendoza-Jonas
2016-07-05 22:41 ` Patrick Williams
2016-07-06 19:08 ` Romain Naour
2016-07-06 20:56 ` Yann E. MORIN
2016-06-29 5:06 ` [Buildroot] [PATCH v3 3/6] Makefile: Generate %_defconfig recipes from macro Sam Bobroff
2016-06-29 5:06 ` [Buildroot] [PATCH v3 4/6] Makefile: Support nested config directories Sam Bobroff
2016-06-29 5:06 ` [Buildroot] [PATCH v3 5/6] Makefile: Add nested config dirs to list-defconfigs Sam Bobroff
2016-06-29 5:06 ` [Buildroot] [PATCH v3 6/6] Makefile: Add merged defconfigs " Sam Bobroff
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=20160705081644.6fd47292@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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