[OE-core] how can i tell which default kernel config OE started with?

[Bruce Ashfield]

On Tue, May 3, 2016 at 6:53 AM, Robert P. J. Day <rpjday at crashcourse.ca>
wrote:

>
>   (actually, working in wind river linux but i suspect the answer will
> be the same.)
>
>   i've defined a target board and, rather than supplying a full
> "defconfig" file as a starting point for kernel configuration, my BSP
> layer starts by applying a "kernel_baseline.cfg" file which contains
> only a couple hundred settings that i am particularly interested in.
>
>   so, given that, how can i tell what OE chose as a starting point for
> a .config file before beginning to apply my kernel config fragments?
> i'm poking around in the log files of the build, but i can't seem to
> see where the "configme" process selects a starting point. am i just
> missing the obvious? i want to see the .config file *before* any of my
> fragments are applied.
>

If you haven't specified a defconfig (in-tree, or in your layer), and are
only using fragments, then it will
be the first fragment. There's no logic to go out and find a baseline,
since it would almost always not
be what someone wanted.

Cheers,

Bruce


>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160503/a3bad93c/attachment-0002.html>