All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juraj Hercek <juraj.hercek@jhksoftware.com>
To: openembedded-core@lists.openembedded.org
Subject: meta-toolchain-qte and wrong paths to QT tools
Date: Wed, 21 Dec 2011 15:56:30 +0100	[thread overview]
Message-ID: <4EF1F39E.60903@jhksoftware.com> (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



             reply	other threads:[~2011-12-21 15:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 14:56 Juraj Hercek [this message]
2011-12-21 15:16 ` meta-toolchain-qte and wrong paths to QT tools 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
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=4EF1F39E.60903@jhksoftware.com \
    --to=juraj.hercek@jhksoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.