Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: meta-toolchain-qte and wrong paths to QT tools
Date: Wed, 21 Dec 2011 22:22:40 +0400	[thread overview]
Message-ID: <jct88c$ajb$1@dough.gmane.org> (raw)
In-Reply-To: <4EF1F39E.60903@jhksoftware.com>

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

On 12/21/2011 06:56 PM, Juraj Hercek wrote:
> Hello list,
>
> I've two questions:
>
> 1) When I build meta-toolchain-qte (c2de8d4 metadata revision) and
> install the resulting sdk, I see two directories in /usr/local/:
> oecore-i686-arm and oecore-i686-i686. What is a rationale behind having
> these two directories instead of one i.e.: oecore-i686-arm?

Because oecore-i686-i686 holds files that are created on i686 to be used 
on i686. They will be common for arm meta-toolchain-qte, mips 
meta-toolchain-qte, powerpc meta-toolchain-qte, etc.

> 2) The oecore-i686-arm/environment-setup-armv5te-oe-linux-gnueabi script
> sets paths to the QT tools which should be installed in oecore-i686-arm
> directory, but they are not. These tools are installed under
> oecore-i686-i686 directory. Changing the path in
> environment-setup-armv5te-oe-linux-gnueabi after toolchain installation
> is easy, but I do not consider it to be a correct fix (assuming that
> oecore-i686-{arm,i686} directories represents proper toolchain
> structure). What is a proper fix for this issue?

I have the attached patch in my patch queue. Hope this helps.

-- 
With best wishes
Dmitry

[-- Attachment #2: 0001-SDK-generation-fixup-paths.patch --]
[-- Type: text/x-diff, Size: 1712 bytes --]

From 80adbc460fa3abd595f1e4c37e402fb2ba51cba4 Mon Sep 17 00:00:00 2001
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Date: Sun, 18 Dec 2011 22:27:49 +0400
Subject: [PATCH] SDK generation: fixup paths

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
---
 meta/conf/bitbake.conf                     |    3 ++-
 meta/recipes-qt/meta/meta-toolchain-qte.bb |    2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 1c21616..9af6faa 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -359,8 +359,9 @@ DEPLOY_DIR_TOOLS = "${DEPLOY_DIR}/tools"
 PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
 
 SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"
+SDK_NATIVE_NAME = "oecore-${SDK_ARCH}-${BUILD_ARCH}"
 SDKPATH = "/usr/local/${SDK_NAME}"
-SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
+SDKPATHNATIVE = "/usr/local/${SDK_NATIVE_NAME}/sysroots/${SDK_SYS}"
 
 ##################################################################
 # Kernel info.
diff --git a/meta/recipes-qt/meta/meta-toolchain-qte.bb b/meta/recipes-qt/meta/meta-toolchain-qte.bb
index 735ccd1..a0d13bd 100644
--- a/meta/recipes-qt/meta/meta-toolchain-qte.bb
+++ b/meta/recipes-qt/meta/meta-toolchain-qte.bb
@@ -30,5 +30,5 @@ toolchain_create_sdk_env_script_append() {
 
     # make a symbolic link to mkspecs for compatibility with Nokia's SDK
     # and QTCreator
-    (cd ${SDK_OUTPUT}/${QT_TOOLS_PREFIX}/..; ln -s ${SDKTARGETSYSROOT}/usr/share/qtopia/mkspecs mkspecs;)
+    (cd ${SDK_NATIVE_OUTPUT}/${QT_TOOLS_PREFIX}/..; ln -s ${SDKTARGETSYSROOT}/usr/share/qtopia/mkspecs mkspecs;)
 }
-- 
1.7.7.3


  parent reply	other threads:[~2011-12-21 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 14:56 meta-toolchain-qte and wrong paths to QT tools Juraj Hercek
2011-12-21 15:16 ` Eric Bénard
2011-12-21 15:48   ` Juraj Hercek
2011-12-21 18:22 ` Dmitry Eremin-Solenikov [this message]
2011-12-21 23:35   ` Eric Bénard
2011-12-22 13:48     ` Dmitry Eremin-Solenikov
2011-12-22 13:57   ` Juraj Hercek

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='jct88c$ajb$1@dough.gmane.org' \
    --to=dbaryshkov@gmail.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