Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-toolchain-qte produces toolchain with missing Qt include dirs
Date: Thu, 01 Jul 2010 20:27:35 +0800	[thread overview]
Message-ID: <4C2C89B7.6040709@freyther.de> (raw)
In-Reply-To: <4C2C5912.80308@jak.nl>

On 07/01/2010 05:00 PM, Arjan wrote:
> I'm trying to build the sdk as described in de OE manual.
> [http://docs.openembedded.org/usermanual/usermanual.html#id501110]
> I did not modify the qt4-embedded.inc or qt4.inc.
> The final sdk archive misses almost all the includes from de Qt
> framework (it only has qtopia/QtCore and qtopia/phonon) . But it does
> include the libs and binaries.
> 
> Is this expected behaviour or am I doing something wrong?

Well, if the example in the manual to build an application doesn't work,
then it is obviously broken...



  reply	other threads:[~2010-07-01 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01  9:00 meta-toolchain-qte produces toolchain with missing Qt include dirs Arjan
2010-07-01 12:27 ` Holger Freyther [this message]
2010-07-01 12:30 ` meta-toolchain-qte produces toolchain with missing Qt includedirs Hauser, Wolfgang (external)

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=4C2C89B7.6040709@freyther.de \
    --to=holger+oe@freyther.de \
    --cc=openembedded-devel@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