[OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

[Mark Hatle]

On 8/13/13 12:40 PM, Laszlo Papp wrote:
> On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle <mark.hatle at windriver.com
> <mailto:mark.hatle at windriver.com>> wrote:
>
>     On 8/13/13 12:23 PM, Laszlo Papp wrote:
>
>         s/which files/which lines/
>
>
>     The kernel configuration mechanism has a tool that will combine the original
>     configuration, and any listed configuration fragments (.cfg files).  It will
>     combine these, and then filter them in such a way that last-in wins.
>
>     See the Yocto Project Linux Kernel Development manual, section 2.2.3:
>
>     http://www.yoctoproject.org/__docs/current/kernel-dev/__kernel-dev.html#changing-the-__configuration
>     <http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration>
>
>
> Could you please clarify how that is related to my question? What I wanna
> understand is: I set something in the config as I wish, and then the bitbake
> file is getting chopped respectively like with "ifdef/elif" etc in C/C++, but
> this time inside the python script defined in the bitbake file.

You asked: How will this know which lines exactly to disregard in the busybox 
include file (".inc")?

My answer is that, according to the quoted documentation, the tooling, as 
described in the above URL, does this as a last-in processing, based on the 
filename(s) of the SRC_URI components.

> I am well aware of that you can customize the defconfig, but my question was
> about the python function.

Specifically for the busybox package, the python fragement "find_cfgs(d):" 
located in the busybox.inc file finds the .cfg files, and collects them into a 
list.  They are then processed by the 'merge_config.sh' script that is called as 
part of the do_configure task.

I believe the merge_config script is provided as part of the linux-libc-headers 
or linux-yocto package, but I may be incorrect on that.

--Mark