Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/12 V2] Fixes for multilib and eSDK
Date: Thu, 18 Jan 2018 11:29:46 +0000	[thread overview]
Message-ID: <1516274986.24502.4.camel@linuxfoundation.org> (raw)
In-Reply-To: <af2c70ff-edfa-fa06-b669-3fdce584b024@windriver.com>

On Thu, 2018-01-18 at 17:35 +0800, Robert Yang wrote:
> Two of the patches have been merged, so I rebased others and put them
> to:
> 
>    git://git.openembedded.org/openembedded-core-contrib rbt/multilib
>    http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/
> multilib
> 
> Robert Yang (10):
>    staging.bbclass: fix for multilib
>    populate_sdk_ext.bbclass: fix for multilib
>    staging.bbclass: staging_populate_sysroot_dir(): fix for multilib
>    staging.bbclass: print searched manifest when not found
>    staging.bbclass: extend_recipe_sysroot(): search multilib manifest
>    package_manager.py: reverse archs correctly
>    multilib.bbclass: extend allarch recipes
>    toolchain-scripts.bbclass: only install all MULTILIB_VARIANTS for
>      image
>    multilib.bbclass: deltask populate_sdk and populate_sdk_ext
>    populate_sdk_ext.bbclass: remove the try...finally

Just to update, I also have a set of patches which alter the manifest
code in staging.bbclass, I wanted to compare what we're doing and
likely create a combination of those patches.

For the deltask commit, could you make it bb.build.deltask() only when
image.bbclass is inherited?

Cheers,

Richard


  reply	other threads:[~2018-01-18 11:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  9:32 [PATCH 00/12 V2] Fixes for multilib and eSDK Robert Yang
2018-01-08  9:32 ` [PATCH 01/12] staging.bbclass: fix for multilib Robert Yang
2018-01-08  9:32 ` [PATCH 02/12] populate_sdk_ext.bbclass: " Robert Yang
2018-01-08  9:33 ` [PATCH 03/12] sstate.bbclass: sstate_hardcode_path(): " Robert Yang
2018-01-08  9:33 ` [PATCH 04/12] staging.bbclass: staging_populate_sysroot_dir(): " Robert Yang
2018-01-08  9:33 ` [PATCH 05/12] staging.bbclass: print searched manifest when not found Robert Yang
2018-01-08  9:33 ` [PATCH 06/12] staging.bbclass: extend_recipe_sysroot(): search multilib manifest Robert Yang
2018-01-08  9:33 ` [PATCH 07/12] package_manager.py: reverse archs correctly Robert Yang
2018-01-08  9:33 ` [PATCH 08/12] multilib.bbclass: remove invalid PACKAGE_INSTALL Robert Yang
2018-01-08  9:33 ` [PATCH 09/12] multilib.bbclass: extend allarch recipes Robert Yang
2018-01-08  9:33 ` [PATCH 10/12] toolchain-scripts.bbclass: only install all MULTILIB_VARIANTS for image Robert Yang
2018-01-08  9:33 ` [PATCH 11/12] multilib.bbclass: deltask populate_sdk and populate_sdk_ext Robert Yang
2018-01-08  9:33 ` [PATCH 12/12] populate_sdk_ext.bbclass: remove the try...finally Robert Yang
2018-01-08 10:04 ` ✗ patchtest: failure for Fixes for multilib and eSDK (rev2) Patchwork
2018-01-08 10:12   ` Robert Yang
2018-01-18  9:35 ` [PATCH 00/12 V2] Fixes for multilib and eSDK Robert Yang
2018-01-18 11:29   ` Richard Purdie [this message]
2018-01-18 13:31     ` Robert Yang

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=1516274986.24502.4.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.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