Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol
On 30/03/2015 21:27, Burton, Ross wrote:
On 30 March 2015 at 18:36, Alex J Lennon
ajlen...@dynamicdevices.co.uk mailto:ajlen...@dynamicdevices.co.uk
wrote:
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.
The devshell drops you into whatever ${S} is for that recipe, which
for the kernel is ${STAGING_KERNEL_DIR} since the kernel
optimisations. For the kernel yes, this is sub-optimal. Maybe the
kernel should override this using the variable I added (as Bruce
mentioned).
Thanks Ross, Bruce for the feedback and pointers. I shall work through.
One thought - it might perhaps be helpful to have two command variants
to easily drop into either place from the command line without having to
worry about environment variables?
e.g. bitbake -c devshell-shared and bitbake -c devshell or some such?
Regards, Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol
On 31 March 2015 at 07:37, Alex J Lennon ajlen...@dynamicdevices.co.uk wrote: One thought - it might perhaps be helpful to have two command variants to easily drop into either place from the command line without having to worry about environment variables? e.g. bitbake -c devshell-shared and bitbake -c devshell or some such? Only gcc and the kernel have the concept of shared sources, so I'm not sure this actually gains much at the cost of more tasks to confuse people. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto master work-shared, kernel .config seems to have gone awol
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. (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. 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? 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 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol
On 30 March 2015 at 18:36, Alex J Lennon ajlen...@dynamicdevices.co.uk
wrote:
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.
The devshell drops you into whatever ${S} is for that recipe, which for the
kernel is ${STAGING_KERNEL_DIR} since the kernel optimisations. For the
kernel yes, this is sub-optimal. Maybe the kernel should override this
using the variable I added (as Bruce mentioned).
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol
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 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
