Commit Message

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.

Comments

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

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

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.