From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt4 GLES (once again)
Date: Wed, 23 Dec 2009 15:30:00 +0100 [thread overview]
Message-ID: <hgt9h8$25m$1@ger.gmane.org> (raw)
In-Reply-To: <hglsin$2vi$2@ger.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20-12-09 20:05, Koen Kooi wrote:
> On 19-12-09 08:54, Holger Hans Peter Freyther wrote:
>> Hi Koen, All,
>>
>> we have the GLES problem once again in the Qt4 recipes. My opinion is
>> still
>> the same that a "bitbake meta-toolchain-qte" should work without
>> requiring
>> downloading proprietary stuff from TI/PowerVR.
>
> Exactly
>
>> From what I think to know, the only difference between GLES and the
>> non GLES
>> recipe is that we have one plugin more. Koen could you help me to
>> verify that?
>
> For qt/e it's one plugin more (a gfxdriver) and library (openvg) and for
> qt/x11 it's one plugin (gldriver) + 2 libs (opengl + openvg) more.
It looks like it also changes stuff in libQtGui(E) :(
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLMiloMkyGM64RGpERAsCYAKCu7ora2XgofUYjPZaznsbySr8x2QCglffO
97qYBGfnD1kQZYXvVm4/sNk=
=FvSK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-12-23 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 7:54 Qt4 GLES (once again) Holger Hans Peter Freyther
2009-12-20 19:05 ` Koen Kooi
2009-12-23 14:30 ` Koen Kooi [this message]
2010-01-01 12:48 ` Holger Hans Peter Freyther
2010-01-02 8:28 ` Koen Kooi
2010-01-04 7:40 ` Holger Hans Peter Freyther
2010-01-04 8:21 ` Koen Kooi
2010-01-04 10:25 ` Holger Hans Peter Freyther
2010-01-04 10:35 ` Koen Kooi
2010-01-04 13:30 ` Holger Hans Peter Freyther
2010-01-06 9:20 ` Holger Hans Peter Freyther
-- strict thread matches above, loose matches on Subject: below --
2010-01-14 13:28 Martin Jansa
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='hgt9h8$25m$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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