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: Thu, 22 Dec 2011 17:48:23 +0400	[thread overview]
Message-ID: <jcvci7$nff$1@dough.gmane.org> (raw)
In-Reply-To: <4EF26D31.9050209@eukrea.com>

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




  reply	other threads:[~2011-12-22 13:57 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
2011-12-21 23:35   ` Eric Bénard
2011-12-22 13:48     ` Dmitry Eremin-Solenikov [this message]
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='jcvci7$nff$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