Openembedded Core Discussions
 help / color / mirror / Atom feed
From: rebecca.swee.fun.chang@intel.com
To: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Cc: Internal Core dev Mailing List <core-dev@eclists.intel.com>
Subject: [PATCHv3 0/2] devshell: make sure toolchains are populated in sysroot
Date: Tue, 30 May 2017 09:42:33 +0800	[thread overview]
Message-ID: <cover.1496107463.git.rebecca.swee.fun.chang@intel.com> (raw)

From: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>

Rework on PATCHv2.
addtask do_prepare_recipe_sysroot is having the same effect on building
more dependencies for devshell.

The 2nd patch in series is to clean up some trailing whitespaces within
devshell.bbclass.

I have done some tests on random recipe to ensure this change is having the
same behavior as the previous implementation.

Thanks.

Regards,
Rebecca

The following changes since commit 27200a3afd606df7f8e592439a8dd403d714ea6f:

  bind: build with threads and update configure options (2017-05-29 15:15:20 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib rebeccas/11464-devshell
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rebeccas/11464-devshell

Chang Rebecca Swee Fun (2):
  devshell.bbclass: ensure toolchains available for do_devshell
  devshell.bbclass: clean up trailing whitespaces

 meta/classes/devshell.bbclass | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

-- 
2.7.4



             reply	other threads:[~2017-05-30  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  1:42 rebecca.swee.fun.chang [this message]
2017-06-05  1:15 ` [PATCHv3 0/2] devshell: make sure toolchains are populated in sysroot Chang, Rebecca Swee Fun
2017-06-05  8:22   ` Richard Purdie

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=cover.1496107463.git.rebecca.swee.fun.chang@intel.com \
    --to=rebecca.swee.fun.chang@intel.com \
    --cc=core-dev@eclists.intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox