From: Christian Gagneraud <chgans@gna.org>
To: Denys Dmytriyenko <denys@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [Qt5] mkspecs/devices: beagleboard == am335x ?
Date: Sun, 28 Jul 2013 08:05:52 +1200 [thread overview]
Message-ID: <51F42820.9010104@gna.org> (raw)
In-Reply-To: <20130727034153.GG3558@edge>
On 07/27/2013 03:41 PM, Denys Dmytriyenko wrote:
> On Sun, Jul 28, 2013 at 03:18:05AM +1200, Christian Gagneraud wrote:
>> On 07/27/2013 02:20 PM, Sundareson, Prabindh wrote:
>>> The device approach is useful for adding platform specific hooks for
>>> eglfs via EGLFS_PLATFORM_HOOKS_SOURCES, so it is a good thing. So it is
>>> more of a convenience/cleaner way, than anything related to performance.
>>>
>>
>> I do agree with Dennys about the compiler flags, yocto knows what
>> are the best flags for the machine/device.
>> What is nice with the device file approach is the specification for
>> OpenGL includes, libs, QPA and the EGLFS hooks as well.
>> Basically I like the fact that all the OpenGL "mess" is sorted out
>> in one place (when it comes to compilation).
>> Interesting examples are the Rasberry Pi [1] and Freescale i.mx6 [2].
>>
>> when considering Qt alone (out of Yocto/OE), I think as a SoC
>> vendor, it is the best way to make sure your users get the best of
>> Qt5/OpenGL, and very easily according to [3] (not tested).
>>
>>
>> When it comes to Yocto, I didn't see any easy way for meta-bsp to
>> tell meta-qt5 how to configure/build qt5 w/ OpenGL support.
>> It seems to me that the only way is through the .bbappend, in qtbase.inc:
>> [...]
>> # if you want to enable egl/gles2 in your .bbappend, don't forget to
>> add right dependencies, e.g.
>> # GL_DEPENDS = "virtual/libgles2 virtual/egl"
>> # QT_GLFLAGS = "-opengl es2 -eglfs"
>> GL_DEPENDS ?= "virtual/libgl"
>> QT_GLFLAGS ?= "-opengl"
>> [...]
>>
>> Could/should this be used by the meta-ti layer?
>>
>> I spent some time recently going through meta-qt5 recently (as well
>> as the qt4 stuff), I even tried an alternative configure/method, so
>> far unsuccessfully. My feeling is that meta-qt5 tries to adapt qt5
>> to OE, I think it should be done the other way around, that's my
>> very personal view.
>>
>> I really would like to see a Yocto Qt5 SDK one of these days.
>>
>> Prabindh, could you tell more about the status of Qt5/OpenGL for TI
>> SoCs, what about this commit [4]? Is it possible to build within
>> Yocto Qt5 w/ OpenGL support for AM335x platforms?
>
> Have you seen this thread:
> http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/2139
No I haven't up to now, thanks for the link.
Regards,
Chris
>
prev parent reply other threads:[~2013-07-27 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 22:45 [Qt5] mkspecs/devices: beagleboard == am335x ? Christian Gagneraud
2013-07-26 21:06 ` Denys Dmytriyenko
2013-07-27 2:20 ` Sundareson, Prabindh
2013-07-27 15:18 ` Christian Gagneraud
2013-07-27 3:41 ` Denys Dmytriyenko
2013-07-27 20:05 ` Christian Gagneraud [this message]
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=51F42820.9010104@gna.org \
--to=chgans@gna.org \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.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.