[Buildroot] [PATCH v3 2/6] Add documentation for merged defconfigs

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Tue Jul 5 06:16:44 UTC 2016

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

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 Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering

More information about the buildroot mailing list