Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: meta-toolchain-sdk build dir names
Date: Tue, 09 Aug 2011 17:25:05 +0100	[thread overview]
Message-ID: <1312907105.14274.310.camel@rex> (raw)
In-Reply-To: <6D5D2EC4-D6E1-4445-9048-66DA9BCF3A81@kernel.crashing.org>

On Tue, 2011-08-09 at 10:46 -0500, Kumar Gala wrote:
> When we do a build we get something like:
> 
> opt/poky/1.0+snapshot/sysroots/powerpc-poky-linux
> 
> Where does the 'powerpc-poky-linux' name come from?
> 
> I think this needs to be more specific to the build if required because of how AVAILTUNES, etc are set.
> 
> So something like:
> 
> opt/poky/1.0+snapshot/sysroots/ppc603e-poky-linux

Agreed, this is a problem with how we're currently setting up the sdk
structure. Something like this will likely fix it:

diff --git a/meta/classes/populate_sdk.bbclass b/meta/classes/populate_sdk.bbclass
index 0f3591b..8c19e83 100644
--- a/meta/classes/populate_sdk.bbclass
+++ b/meta/classes/populate_sdk.bbclass
@@ -5,7 +5,7 @@ SDK_DIR = "${WORKDIR}/sdk"
 SDK_OUTPUT = "${SDK_DIR}/image"
 SDK_DEPLOY = "${TMPDIR}/deploy/sdk"
 
-SDKTARGETSYSROOT = "${SDKPATH}/sysroots/${TARGET_SYS}"
+SDKTARGETSYSROOT = "${SDKPATH}/sysroots/${MULTIMACH_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"

Cheers,

Richard




      reply	other threads:[~2011-08-09 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 15:46 meta-toolchain-sdk build dir names Kumar Gala
2011-08-09 16:25 ` Richard Purdie [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=1312907105.14274.310.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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