From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt4 GLES (once again)
Date: Sat, 02 Jan 2010 09:28:18 +0100 [thread overview]
Message-ID: <hhn031$6hg$1@ger.gmane.org> (raw)
In-Reply-To: <201001011348.44168.holger+oe@freyther.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01-01-10 13:48, Holger Hans Peter Freyther wrote:
> On Wednesday 23 December 2009 15:30:00 Koen Kooi wrote:
>> On 20-12-09 20:05, Koen Kooi wrote:
>
>> It looks like it also changes stuff in libQtGui(E) :(
>
> it does, it is compiling the egl and OpenVG part into libQtGui...
>
>
> what about something like this? This way one can select qt4-embedded as
> default and switch to the gles variant when ones needs it?
If that works, I can live with that.
regards,
Koen
>
>
>
> diff --git a/recipes/qt4/qt4-embedded-gles_4.6.0.bb b/recipes/qt4/qt4-embedded-
> gles_4.6.0.bb
> index f819c66..06cdcc5 100644
> --- a/recipes/qt4/qt4-embedded-gles_4.6.0.bb
> +++ b/recipes/qt4/qt4-embedded-gles_4.6.0.bb
> @@ -1,6 +1,7 @@
> require qt4-embedded.inc
> PR = "${INC_PR}.0"
>
> +PROVIDES += "qt4-embedded"
> QT_GLFLAGS = "-opengl es2 -openvg"
>
> require qt-4.6.0.inc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLPwOiMkyGM64RGpERAmelAJwJd3cqDmXGpbvEidLqG5CW/bhOPgCeOjzV
uXKmwv73mpZgYn2LWi9kXCA=
=2TBV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-02 8:30 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
2010-01-01 12:48 ` Holger Hans Peter Freyther
2010-01-02 8:28 ` Koen Kooi [this message]
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='hhn031$6hg$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