Re: yocto master work-shared, kernel .config seems to have gone awol

[Bruce Ashfield <bruce.ashfield@windriver.com>]

On 2015-03-30 01:36 PM, Alex J Lennon wrote:
> Hi,
>
> I'm updating to Yocto master and have been seeing that when I bitbake -c
> devshell virtual/kernel I go into a work-shared tree now.

There was a discussion on the list about this. See the patch from
Ross:

[OE-core] [PATCH] devshell: allow the starting directory to be overridden

Since there are those that want to be in the source dir, and those
that want to be in the build dir .. there's a variable to make that
change.

>
> (This is all with meta-fsl-arm)
>
> I'd normally change the kernel configuration with bitbake -c menuconfig
> virtual/kernel then pull out the .config and make my changes to
> defconfig as needed.

In this case, you need to be in the source tree, but have your output
pointing to the build dir.

That used to be set when you dropped into the devshell, check and see
if KBUILD_OUTPUT is set.

>
> But I can't seem to find it any more, either in work-shared or if I
> traverse to the work tree.
>
> No doubt my own stupidity here but where is it supposed to be nowadays?
>
> Could anybody point me to a discussion on how things are going to be
> broken out into work-shared and (presumably) work so I can get up to speed?

Most of the changes are documented in the commits that make the switch,
and you'll see them proposed on the oe-core mailing list by Richard,
with me following up with comments and details.

Bruce

>
> Not finding the configuration I thought I'd try generating a kernel
> fragment with bitbake  -c diffconfig virtual/kernel from the Yocto docs
> but I can't see a fragment.cfg anywhere in the tree
>
> I guess this could all be just that meta-fsl-arm isn't quick in sync
> with current the current master? (assuming it's not the more likely
> explanation that I just have this plain wrong)
>
> Thanks,
>
> Alex
>