From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-kde] Test images (was: Re: [OE-core] RFC: Porting KDE Plasma Active (WIP))
Date: Wed, 02 May 2012 16:55:53 +0200 [thread overview]
Message-ID: <jnrhu6$cgo$1@dough.gmane.org> (raw)
In-Reply-To: <CAGiJk9e+V8jZWaDR092pTYcC2FJWxKcOsoGzXX5F777gC3yW=g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 23-04-12 15:49, Samuel Stirtzel schreef:
> 2012/4/23 Koen Kooi <koen@dominion.thruhere.net>:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Op 23-04-12 09:17, Samuel Stirtzel schreef:
>>> 2012/4/20 Koen Kooi <koen@dominion.thruhere.net>:
>>
>>> And do you have a bbappend for qt to enable GLES?
>>>
>>>> The "recipes-misc-support/qt4-x11-free_4.8.0.bbappend" [1] enables
>>>> GLES for Qt on the soc family omap3.
>>
>> Actually it doesn't :) That enables EGL mode, but 'desktop GL' as Qt
>> calls it:
>>
>> OpenGL support ......... yes (Desktop OpenGL)
>>
>> So I did:
>>
>> +++ b/recipes-misc-support/qt4-x11-free_4.8.0.bbappend @@ -1,7 +1,7 @@
>> - -QT_GLFLAGS_omap3 = "-egl" +QT_GLFLAGS_omap3 = "-opengl es2 "
>>
>> And I get:
>>
>> [koen@Angstrom-F16-vm-rpm qt4-x11-free-4.8.0-r43.1]$ grep OpenGL
>> temp/log.do_configure OpenGL ES 2.x auto-detection... () OpenGL ES 2.x
>> enabled. OpenGL support ......... yes (OpenGL ES 2.x)
>
> Interesting, seems like I have been fooled by Qt:
>
> OpenGL support ......... yes (Desktop OpenGL) EGL support ............
> yes <EGL/egl.h>
>
> For me this sounded as if it was configured right, so "EGL support" is a
> bit misleading..
>
>>
>> I'm going to see if that actually builds. If so, I'll send a patch to
>> fix it and add more TI opengl platforms. And I'll poke my ex coworkers
>> about having a bbappend in meta-ti to enable opengl for the respective
>> platforms, doing it in meta-kde feels wrong, but works for me at the
>> moment.
>
> TBH it wasn't properly tested yet. On my Overo every time I start any EGL
> application all I get is just EGL_BAD_ALLOC 0x3003 ...
That turned out to be a bug in opkg :( With the latest patchset I posted to
meta-ti the bug should be gone.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPoUr3AAoJEHZqAkdh1vT6iTkP+QG4MWihg/A1/QGEWLlLMJXD
OYaP1QOMLyQrmaN72p8sH8AInL3z8jEOC3+FXLDN/tn71qJVRuwwKHYUh0vEcR8N
X285jnArDnuHGgGkUZyMPGeniZHlBIBAuBvvFveZR371OEOKaVHZRcA7gm2Pl7D/
FgRG/jInNXxcwkkKgx28z34C9mQLwsLEAlzbVPvolzufFg9ggK3fQ7cT0OjNOc84
cPZjyuVEpuZqB/Ie4DQ7JcY9sI7Sp3s54+j0LcRF6dpXsqALYlNx+0khz94wdhVt
1uOBucVSQwRBuDbhzcnMNN9768wHa/lAEQXJflUL2N8B/doh5kA+b7Fqk+e1xwn/
PuAdNEMUaL/ywhFumatVqo1hjrGLGRm6+oymGdKGtWjaBDcbsQb7bOlR7z/NghVS
K4OVjqZiCkThihd22Nu7deSaQg3mZ7oowkAOALSDR80IJjSwmt08iRFV2szan7OU
z9l1xe3eVwlsbMFuoYwn37wlRpiUa9Sp1sZE9NfLL4E1ssV/nKFDwQz1Qo8YNq8q
5/Hh4UzaIlW7FhVQf+/YD3rFjNrpRTbKKuoRzBzXLjL3Q+mnbzKDW/e/Aqvm3lQn
h5bRECO45VanBFHoN9QQPD2MtGrsm/NoavDYvSsxk14Q5ePDkTwqrMIbrGKAaMQF
AAW1YHfhbUe7l/UqvvwY
=9qq6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-05-02 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 15:19 [meta-kde] Test images (was: Re: [OE-core] RFC: Porting KDE Plasma Active (WIP)) Samuel Stirtzel
2012-04-18 17:16 ` Koen Kooi
2012-04-19 9:09 ` Samuel Stirtzel
2012-04-19 9:12 ` Samuel Stirtzel
2012-04-19 9:40 ` Koen Kooi
2012-04-19 14:03 ` Samuel Stirtzel
2012-04-19 16:57 ` Koen Kooi
2012-04-20 5:32 ` Koen Kooi
2012-04-20 7:59 ` Samuel Stirtzel
2012-04-20 10:24 ` Koen Kooi
2012-04-20 10:45 ` Samuel Stirtzel
2012-04-20 10:55 ` Koen Kooi
2012-04-20 11:28 ` Samuel Stirtzel
2012-04-20 15:41 ` Koen Kooi
2012-04-23 7:17 ` Samuel Stirtzel
2012-04-23 12:47 ` Koen Kooi
2012-04-23 13:49 ` Samuel Stirtzel
2012-05-02 14:55 ` Koen Kooi [this message]
2012-05-03 9:46 ` Samuel Stirtzel
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='jnrhu6$cgo$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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 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.