On 31 March 2015 at 07:37, Alex J Lennon
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 s
On 30/03/2015 21:27, Burton, Ross wrote:
>
> On 30 March 2015 at 18:36, Alex J Lennon
> 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
On 30 March 2015 at 18:36, Alex J Lennon
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} sin
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 sta
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 chan
