Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] devshell.bbclass: ensure toolchains available for do_devshell
Date: Tue, 30 May 2017 08:41:43 +0100	[thread overview]
Message-ID: <1496130103.25229.155.camel@linuxfoundation.org> (raw)
In-Reply-To: <1601098.y1ZEXWJiEU@peggleto-mobl.ger.corp.intel.com>

On Tue, 2017-05-30 at 12:07 +1200, Paul Eggleton wrote:
> Hi Richard,
> 
> On Tuesday, 30 May 2017 11:31:36 AM NZST Richard Purdie wrote:
> > 
> > On Mon, 2017-05-29 at 13:16 +0800, Chang Rebecca Swee Fun wrote:
> > > 
> > > Toolchains are required to be prepopulated in sysroot before
> > > entering devshell.
> > > 
> > > [YOCTO #11464]
> > > 
> > > Signed-off-by: Chang Rebecca Swee Fun 
> > > ---
> > >  meta/classes/devshell.bbclass | 11 ++++++++++-
> > >  1 file changed, 10 insertions(+), 1 deletion(-)
> > This looks awfully complicated and I'm not sure this does much more
> > than this would:
> > 
> > -addtask devshell after do_patch
> > +addtask devshell after do_prepare_recipe_sysroot
> > 
> > Can someone explain to me why we want to do the below instead as I
> > think the effect is the same?
> > 
> > I did read the bug too but that didn't help answer my question.
> > 
> > Yes, this does mean devshell will now trigger a lot of more
> > dependencies and build but I think the change below would do the
> > same
> > thing too.
> I'd suggested the method Rebecca is using in the bug, but you're
> right, I'm 
> not sure why I didn't think of doing as you suggest instead.
> Presumably 
> however since do_prepare_recipe_sysroot doesn't depend on do_patch we
> would 
> still need to depend on that i.e.:
> 
> addtask devshell after do_patch do_prepare_recipe_sysroot
> 
> Right?

Yes, you're right that we still need do_patch too.

Cheers,

Richard





  reply	other threads:[~2017-05-30  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29  5:16 [PATCH 0/2] devshell: make sure toolchains are populated in sysroot Chang Rebecca Swee Fun
2017-05-29  5:16 ` [PATCH 1/2] devshell.bbclass: ensure toolchains available for do_devshell Chang Rebecca Swee Fun
2017-05-29 23:31   ` Richard Purdie
2017-05-30  0:07     ` Paul Eggleton
2017-05-30  7:41       ` Richard Purdie [this message]
2017-05-29  5:16 ` [PATCH 2/2] devshell.bbclass: clean up trailing whitespaces Chang Rebecca Swee Fun

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=1496130103.25229.155.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox