From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 8/8] fix SDK building due TARGET_ARCH use in installation path
Date: Fri, 08 Jul 2011 16:38:48 +0100 [thread overview]
Message-ID: <1310139528.20015.894.camel@rex> (raw)
In-Reply-To: <73f52ab56a2f932082e954f5650896cdee010fee.1310132765.git.otavio@ossystems.com.br>
On Fri, 2011-07-08 at 13:47 +0000, Otavio Salvador wrote:
> TARGET_ARCH makes the building too fragile since it changes during
> building of target and nativesdk binaries thus making it difficult to
> handle a proper path for installation of binaries. The fix for it is
> to move it to toolchain tarball name.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta/classes/populate_sdk.bbclass | 2 +-
> meta/conf/bitbake.conf | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/populate_sdk.bbclass b/meta/classes/populate_sdk.bbclass
> index 089ed9a..03b6d0f 100644
> --- a/meta/classes/populate_sdk.bbclass
> +++ b/meta/classes/populate_sdk.bbclass
> @@ -9,7 +9,7 @@ SDKTARGETSYSROOT = "${SDKPATH}/sysroots/${TARGET_SYS}"
>
> TOOLCHAIN_HOST_TASK ?= "task-sdk-host-nativesdk task-cross-canadian-${TRANSLATED_TARGET_ARCH}"
> TOOLCHAIN_TARGET_TASK ?= "task-core-standalone-sdk-target task-core-standalone-sdk-target-dbg"
> -TOOLCHAIN_OUTPUTNAME ?= "${SDK_NAME}-toolchain-${DISTRO_VERSION}"
> +TOOLCHAIN_OUTPUTNAME ?= "${SDK_NAME}-${SDK_ARCH}-${TARGET_ARCH}-toolchain-${DISTRO_VERSION}"
>
> RDEPENDS = "${TOOLCHAIN_TARGET_TASK} ${TOOLCHAIN_HOST_TASK}"
> DEPENDS = "virtual/fakeroot-native sed-native"
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index bdaa35d..cc2b8e2 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -341,7 +341,7 @@ DEPLOY_DIR_TOOLS = "${DEPLOY_DIR}/tools"
>
> PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
>
> -SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"
> +SDK_NAME = "oecore-sdk-${DISTRO}"
> SDKPATH = "/usr/local/${SDK_NAME}"
> SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
I'd really like Koen to take a look at this with his Angstrom hat on. I
still suspect the better fix for this is likely to end up with:
SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"
-SDKPATH = "/usr/local/${SDK_NAME}"
+SDKPATH = "/usr/local/oecore-sdk-${DISTRO}"
SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
Certainly having TARGET_ARCH in SDKPATH is a bad idea but I think the
SDK_NAME variable could make sense as it is originally...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-08 15:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:47 [PATCH 0/8] Patches pending for merging from O.S. Systems tree Otavio Salvador
2011-07-08 13:47 ` [PATCH 1/8] Rework how the devshell functions Otavio Salvador
2011-07-08 15:33 ` Richard Purdie
2011-07-08 13:47 ` [PATCH 2/8] oe.terminal: improve how we spawn screen Otavio Salvador
2011-07-08 13:47 ` [PATCH 3/8] cmake.bbclass: use CPPFLAGS and CXXFLAGS Otavio Salvador
2011-07-08 15:34 ` Richard Purdie
2011-07-08 13:47 ` [PATCH 4/8] cmake: refactor recipe Otavio Salvador
2011-07-08 15:27 ` Richard Purdie
2011-07-08 13:47 ` [PATCH 5/8] libarchive: add 2.8.4 version Otavio Salvador
2011-07-08 15:27 ` Richard Purdie
2011-07-08 15:50 ` Otavio Salvador
2011-07-08 16:18 ` Richard Purdie
2011-07-08 16:47 ` Otavio Salvador
2011-07-08 13:47 ` [PATCH 6/8] cmake: add nativesdk and target versions Otavio Salvador
2011-07-08 15:28 ` Richard Purdie
2011-07-08 15:49 ` Otavio Salvador
2011-07-08 16:08 ` Paul Eggleton
2011-07-08 16:22 ` Richard Purdie
2011-07-08 16:36 ` Paul Eggleton
2011-07-08 13:47 ` [PATCH 7/8] cmake: update to 2.8.5-rc3 Otavio Salvador
2011-07-08 15:35 ` Richard Purdie
2011-07-08 15:41 ` Otavio Salvador
2011-07-08 13:47 ` [PATCH 8/8] fix SDK building due TARGET_ARCH use in installation path Otavio Salvador
2011-07-08 15:38 ` Richard Purdie [this message]
2011-07-08 16:12 ` Koen Kooi
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=1310139528.20015.894.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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