meta-toolchain-qte and wrong paths to QT tools

meta-toolchain-qte and wrong paths to QT tools

[Juraj Hercek]

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?

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?

Thank you in advance for your response(s).

Cheers,
Juraj

Re: meta-toolchain-qte and wrong paths to QT tools

[Eric Bénard]

Hi Juraj,

Le 21/12/2011 15:56, Juraj Hercek a écrit :
> 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?
>
> 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?
>
> Thank you in advance for your response(s).
>
did you build a i686 machine before building the arm one in the same tmp ?

I have a similar problem reported here :
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014480.html

Eric

Re: meta-toolchain-qte and wrong paths to QT tools

[Juraj Hercek]

Hi Eric,

On 12/21/2011 04:16 PM, Eric Bénard wrote:
> Hi Juraj,
> 
> Le 21/12/2011 15:56, Juraj Hercek a écrit :
>> 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?
>>
>> 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?
>>
>> Thank you in advance for your response(s).
>>
> did you build a i686 machine before building the arm one in the same tmp ?

AFAIR, I've just "bitbake meta-toolchain-qte" after removing 
build/{bitbake.lock,pseudodone,sstate-cache,tmp-eglibc} files/directories.

> I have a similar problem reported here :
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014480.html

It seems to be the same, or at least very similar problem.

> Eric

--juraj

Re: meta-toolchain-qte and wrong paths to QT tools

[Dmitry Eremin-Solenikov]

[-- 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

Re: meta-toolchain-qte and wrong paths to QT tools

[Eric Bénard]

Hi Dmitry,

Le 21/12/2011 19:22, Dmitry Eremin-Solenikov a écrit :
> 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.
>
there seems to be something wrong here :

-    (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;)


${SDK_NATIVE_OUTPUT} seems undefined.

Eric

Re: meta-toolchain-qte and wrong paths to QT tools

[Dmitry Eremin-Solenikov]

On 12/22/2011 03:35 AM, Eric Bénard wrote:
> Hi Dmitry,
>
> Le 21/12/2011 19:22, Dmitry Eremin-Solenikov a écrit :
>> 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.
>>
> there seems to be something wrong here :
>
> - (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;)
>
>
> ${SDK_NATIVE_OUTPUT} seems undefined.

My fault. I think you can ignore this part of the patch.

>
> Eric


-- 
With best wishes
Dmitry

Re: meta-toolchain-qte and wrong paths to QT tools

[Juraj Hercek]

On 12/21/2011 07:22 PM, Dmitry Eremin-Solenikov wrote:
> 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.

This makes perfect sense. Thank you.

>> 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.

---8<---
-    (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;)
  }
--->8---

I've applied patch but as Eric pointed out earlier, SDK_NATIVE_OUTPUT 
(from the snip above) is not defined anywhere (I've searched the string 
throughout whole oe-core).

Anyways, this snip of code deals with mkspecs, and I am not sure if 
mkspecs should be installed in "i686-arm". My gut feeling would expect 
mkspecs to be in "i686-i686" along with the other QT tools which are 
already in "i686-i686" part.