From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: "Burton, Ross" <ross.burton@intel.com>,
Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Yocto <yocto@yoctoproject.org>
Subject: Re: yocto master work-shared, kernel .config seems to have gone awol
Date: Tue, 31 Mar 2015 08:37:44 +0200 [thread overview]
Message-ID: <551A40B8.2000307@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAJTo0LZ7D4NsVNP155jOy0pRzLCCxrYu_EbSLG60cQU8TN_hfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On 30/03/2015 21:27, Burton, Ross wrote:
>
> On 30 March 2015 at 18:36, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk <mailto:ajlennon@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
[-- Attachment #2: Type: text/html, Size: 2511 bytes --]
next prev parent reply other threads:[~2015-03-31 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 17:36 yocto master work-shared, kernel .config seems to have gone awol Alex J Lennon
2015-03-30 18:33 ` Bruce Ashfield
2015-03-30 19:27 ` Burton, Ross
2015-03-31 6:37 ` Alex J Lennon [this message]
2015-03-31 10:55 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551A40B8.2000307@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=bruce.ashfield@windriver.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.