Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7 v3] Enable the ability to create an image matching SDK
Date: Tue, 03 Jul 2012 10:41:17 -0700	[thread overview]
Message-ID: <4FF32EBD.2050006@linux.intel.com> (raw)
In-Reply-To: <cover.1341262097.git.mark.hatle@windriver.com>

On 07/02/2012 01:50 PM, Mark Hatle wrote:
> Rebased and patch 7/7 added to correct an oversight in base.bbclass.
>
> --- v2
>
> Only difference is patch 1/6, I accidently sent and older broken version of the
> patch.  This is the correct version.
>
> --- v1
>
> After this series of patches, it is possible to generate an SDK that
> matches the image.  The SDK and all related code is only activated if an image
> recipe is built using the "populate_sdk" task, such as:
>
> bitbake core-image-sato -c populate_sdk
>
> Existing SDK images, such as meta-toolchain or meta-toolchain-gmae continue to
> work without modifications.
>
> The following changes since commit 64422f7c5da160050a5454817c8fa9d070104b34:
>
>    package.bbclass: Add missing PKGR, PKGV, PKGE and ALTERNATIVE variables from PACKAGEVARS (2012-07-02 16:44:57 +0100)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib mhatle/sdk
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/sdk
>
> Mark Hatle (7):
>    Fix manual log file paths
>    populate_sdk.bbclass: Split into two parts
>    populate_sdk: Allow for attempt only packages in the SDK
>    populate_sdk_base.bbclass: Change to using task specific depends
>    populate_sdk: enable basic multilib support
>    image.bbclass: Add support to build the SDK in parallel with the
>      image
>    base.bbclass: Add cross-canadian-${TRANSLATED_TARGET_ARCH} to the
>      license exclusion list
>
>   meta/classes/base.bbclass              |    2 +-
>   meta/classes/image.bbclass             |    7 ++-
>   meta/classes/package_deb.bbclass       |    4 +-
>   meta/classes/package_ipk.bbclass       |    2 +-
>   meta/classes/package_rpm.bbclass       |   10 +-
>   meta/classes/populate_sdk.bbclass      |   91 +---------------------
>   meta/classes/populate_sdk_base.bbclass |  128 ++++++++++++++++++++++++++++++++
>   meta/classes/populate_sdk_deb.bbclass  |    6 +-
>   meta/classes/populate_sdk_ipk.bbclass  |    5 +-
>   meta/classes/populate_sdk_rpm.bbclass  |    4 +-
>   meta/classes/rootfs_deb.bbclass        |    2 +
>   meta/classes/rootfs_ipk.bbclass        |    2 +
>   meta/classes/toolchain-scripts.bbclass |   16 +++--
>   13 files changed, 171 insertions(+), 108 deletions(-)
>   create mode 100644 meta/classes/populate_sdk_base.bbclass
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-07-03 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 20:50 [PATCH 0/7 v3] Enable the ability to create an image matching SDK Mark Hatle
2012-07-02 20:50 ` [PATCH 7/7] base.bbclass: Add cross-canadian-${TRANSLATED_TARGET_ARCH} to the license exclusion list Mark Hatle
2012-07-03 17:41 ` Saul Wold [this message]

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=4FF32EBD.2050006@linux.intel.com \
    --to=sgw@linux.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