meta-toolchain-qte and wrong paths to QT tools

DISCUSSION Juraj Hercek 3 participants 7 messages Dec 21, 2011 – Dec 22, 2011

lore

Share & tools

lore

Juraj Hercek

author

2011-12-21 15:03 UTC #0 lore raw

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

Eric Bénard

2011-12-21 15:23 UTC #1 lore raw

Hi Juraj,

Quoted 15 lines · Juraj Hercek

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?

Quoted 2 lines

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

Juraj Hercek

author

2011-12-21 15:55 UTC #2 lore raw

Hi Eric,

Quoted 18 lines · Eric Bénard

Hi Juraj,
Quoted 15 lines · Juraj Hercek
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?

Quoted 3 lines

Quoted 2 lines
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.

Quoted 2 lines

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.

Quoted 1 line

Eric

--juraj

Dmitry Eremin-Solenikov

2011-12-21 18:31 UTC #3 lore raw

In reply to Juraj Hercek

Quoted 8 lines · 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?

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.

Quoted 8 lines

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.

Signature · 2 lines

With best wishes
Dmitry

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

Signed-off-by Dmitry Eremin-Solenikov <[email protected]>

---
 meta/conf/bitbake.conf                     |    3 ++-
 meta/recipes-qt/meta/meta-toolchain-qte.bb |    2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

meta/conf/bitbake.conf +2 -1

index 1c21616..9af6faa 100644
@@ -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.

meta/recipes-qt/meta/meta-toolchain-qte.bb +1 -1

index 735ccd1..a0d13bd 100644
@@ -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;)
 }

Signature · 1 line

1.7.7.3

Eric Bénard

2011-12-21 23:43 UTC #4 lore raw

Hi Dmitry,

Quoted 23 lines · Dmitry Eremin-Solenikov

Quoted 8 lines · 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?
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.
Quoted 8 lines
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?

Quoted 2 lines

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

Dmitry Eremin-Solenikov

2011-12-22 13:57 UTC #5 lore raw

Quoted 32 lines · Eric Bénard

Hi Dmitry,
Quoted 25 lines · Dmitry Eremin-Solenikov
Quoted 8 lines · 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?
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.
Quoted 8 lines
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?
Quoted 2 lines
I have the attached patch in my patch queue. Hope this helps.
there seems to be something wrong here :

Quoted 7 lines

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

Quoted 2 lines

Eric

Signature · 2 lines

With best wishes
Dmitry

Juraj Hercek

author

2011-12-22 14:04 UTC #6 lore raw

In reply to Dmitry Eremin-Solenikov

Quoted 11 lines · Dmitry Eremin-Solenikov

Quoted 8 lines · 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?
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.

Quoted 10 lines

Quoted 8 lines
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.