From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] populate_sdk_base: Extend TOOLCHAIN_TARGET_TASK to include multilib variants
Date: Thu, 24 Jul 2014 16:22:06 -0500 [thread overview]
Message-ID: <53D178FE.6000400@windriver.com> (raw)
In-Reply-To: <1406236149.27697.16.camel@ted>
On 7/24/14, 4:09 PM, Richard Purdie wrote:
> Most people expect the toolchain from a multilib build to contain multilib
> components. This change makes that happen and is easy for users to override
> should they want something different.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I tested this (with ipk works, with rpm doesn't work any less then it did before...)
Acked-by: Mark Hatle <mark.hatle@windriver.com>
> diff --git a/meta/classes/populate_sdk_base.bbclass b/meta/classes/populate_sdk_base.bbclass
> index 0df98db..4b489a6 100644
> --- a/meta/classes/populate_sdk_base.bbclass
> +++ b/meta/classes/populate_sdk_base.bbclass
> @@ -32,7 +32,10 @@ SDKTARGETSYSROOT = "${SDKPATH}/sysroots/${REAL_MULTIMACH_TARGET_SYS}"
>
> TOOLCHAIN_HOST_TASK ?= "nativesdk-packagegroup-sdk-host packagegroup-cross-canadian-${MACHINE}"
> TOOLCHAIN_HOST_TASK_ATTEMPTONLY ?= ""
> -TOOLCHAIN_TARGET_TASK ?= "packagegroup-core-standalone-sdk-target packagegroup-core-standalone-sdk-target-dbg"
> +TOOLCHAIN_TARGET_TASK ?= " \
> + ${@multilib_pkg_extend(d, 'packagegroup-core-standalone-sdk-target')} \
> + ${@multilib_pkg_extend(d, 'packagegroup-core-standalone-sdk-target-dbg')} \
> + "
> TOOLCHAIN_TARGET_TASK_ATTEMPTONLY ?= ""
> TOOLCHAIN_OUTPUTNAME ?= "${SDK_NAME}-toolchain-${SDK_VERSION}"
>
>
>
prev parent reply other threads:[~2014-07-24 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 21:09 [PATCH] populate_sdk_base: Extend TOOLCHAIN_TARGET_TASK to include multilib variants Richard Purdie
2014-07-24 21:22 ` Mark Hatle [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=53D178FE.6000400@windriver.com \
--to=mark.hatle@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