[OE-core] busybox - providing your own defconfig

Peter Bergin peter at berginkonsult.se
Thu Mar 23 10:49:48 UTC 2017


I'm currently looking into the configuration of busybox. What I want to 
do is to have my own defconfig in my own layer added by a bbappend file. 
During configuration of busybox I want use my defconfig file. What 
happens is that my defconfig is used as a base but then a couple of .cfg 
files with config fragments are added to my config.

Since the support of config fragments was added 
(56dc1720caa48344238d352c7b6e9b0f0d41aa54) to the busybox package all 
.cfg files added to the SRC_URI is unconditionally merged to your 
config. Probably an easy fix in my case is to add a do_configure_prepend 
step and remove all .cfg files from my WORKDIR. But my question that I 
want to raise is if this is intended and if it not should be possible to 
have your own untampered defconfig for busybox?

If the .cfg files are always unconditionally merged I can not see the 
benefit of them as you could have them in the default defconfig instead. 
I see in later commits of busybox.inc that some .cfg files now have 
conditionals in the SRC_URI, I think this is the way .cfg files should 
be handled.


More information about the Openembedded-core mailing list