From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Replacing Web in Sato with Midori
Date: Wed, 08 Aug 2012 16:00:50 +0100 [thread overview]
Message-ID: <1503062.H9kskseNSt@helios> (raw)
In-Reply-To: <FC8D60B3-17DE-4CEE-8A86-4BF201870280@dominion.thruhere.net>
On Wednesday 08 August 2012 16:47:05 Koen Kooi wrote:
> Op 8 aug. 2012, om 16:03 heeft Paul Eggleton <paul.eggleton@linux.intel.com>
het volgende geschreven:
> > On Wednesday 08 August 2012 15:56:33 Koen Kooi wrote:
> >> There are a ton of recipes in oe-core that need extra layers to get
> >> properly tested (QT comes to mind),
> >
> > What are you referring to? Qt should be perfectly testable within OE-Core.
>
> What kind of big qt apps does oe-core have to test it? I had to enable
> meta-kde to find bugs in the qt recipes, so if the tests are in there, they
> aren't get run properly.
And? KDE is far more demanding upon Qt than most Qt-based applications. We had
to make specific changes to our Qt recipes just to accommodate it.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-08 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 8:41 Replacing Web in Sato with Midori Burton, Ross
2012-08-08 10:01 ` Koen Kooi
2012-08-08 12:23 ` Richard Purdie
2012-08-08 12:36 ` Martin Jansa
2012-08-08 12:48 ` Richard Purdie
2012-08-09 15:18 ` Martin Jansa
2012-08-08 13:56 ` Koen Kooi
2012-08-08 14:03 ` Paul Eggleton
2012-08-08 14:47 ` Koen Kooi
2012-08-08 15:00 ` Paul Eggleton [this message]
2012-08-08 15:04 ` Samuel Stirtzel
2012-08-08 15:07 ` Paul Eggleton
2012-08-08 10:39 ` Phil Blundell
2012-08-08 12:07 ` Burton, Ross
2012-08-08 12:26 ` Phil Blundell
2012-08-08 12:31 ` Burton, Ross
2012-08-08 12:28 ` Richard Purdie
2012-08-08 16:39 ` Mark Hatle
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=1503062.H9kskseNSt@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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