* [Qt5] mkspecs/devices: beagleboard == am335x ? @ 2013-07-25 22:45 Christian Gagneraud 2013-07-26 21:06 ` Denys Dmytriyenko 0 siblings, 1 reply; 6+ messages in thread From: Christian Gagneraud @ 2013-07-25 22:45 UTC (permalink / raw) To: meta-ti@yoctoproject.org Hi there, In qtbase sources, there are a couple of "device" definitions files, according to [1], this greatly help cross-compiling qt5. This device file specify things for CPU and GPU optimisations. So basically these files are tightly coupled with BSP providers. One of them is linux-beagleboard-g++ [2], is it appropriate to use this one for AM335x based platform as well? The meta-qt5 layer doesn't seem to use this feature, but if it did, would this device config files help to get an optimised Qt5 build for TI SoCs? Especially, would that help to get OpenGL stuff sorted out? Regards, Chris [1] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ [2] https://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-beagleboard-g++ ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qt5] mkspecs/devices: beagleboard == am335x ? 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 0 siblings, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2013-07-26 21:06 UTC (permalink / raw) To: Christian Gagneraud; +Cc: meta-ti@yoctoproject.org On Fri, Jul 26, 2013 at 10:45:02AM +1200, Christian Gagneraud wrote: > Hi there, > > In qtbase sources, there are a couple of "device" definitions files, > according to [1], this greatly help cross-compiling qt5. > This device file specify things for CPU and GPU optimisations. So > basically these files are tightly coupled with BSP providers. > > One of them is linux-beagleboard-g++ [2], is it appropriate to use > this one for AM335x based platform as well? > > The meta-qt5 layer doesn't seem to use this feature, but if it did, > would this device config files help to get an optimised Qt5 build > for TI SoCs? Especially, would that help to get OpenGL stuff sorted > out? > > Regards, > Chris > > [1] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ > [2] https://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-beagleboard-g++ Chris, Looking at those files shows very basic compiler optimization flags being set, -march, -mtune, -mfpu etc. I don't see any GL or GPU specifics in there. It also hardcodes things like soft-fp, which is not good. All this stuff is alredy taken care of by the build framework and I'm sure meta-qt5, like the old qt4, sets all the right COMPILER_FLAGS to get the most performance from the target CPU. -- Denys ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qt5] mkspecs/devices: beagleboard == am335x ? 2013-07-26 21:06 ` Denys Dmytriyenko @ 2013-07-27 2:20 ` Sundareson, Prabindh 2013-07-27 15:18 ` Christian Gagneraud 0 siblings, 1 reply; 6+ messages in thread From: Sundareson, Prabindh @ 2013-07-27 2:20 UTC (permalink / raw) To: Dmytriyenko, Denys, Christian Gagneraud; +Cc: meta-ti@yoctoproject.org 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. regards Prabindh ________________________________________ From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of Dmytriyenko, Denys Sent: Saturday, July 27, 2013 2:36 AM To: Christian Gagneraud Cc: meta-ti@yoctoproject.org Subject: Re: [meta-ti] [Qt5] mkspecs/devices: beagleboard == am335x ? On Fri, Jul 26, 2013 at 10:45:02AM +1200, Christian Gagneraud wrote: > Hi there, > > In qtbase sources, there are a couple of "device" definitions files, > according to [1], this greatly help cross-compiling qt5. > This device file specify things for CPU and GPU optimisations. So > basically these files are tightly coupled with BSP providers. > > One of them is linux-beagleboard-g++ [2], is it appropriate to use > this one for AM335x based platform as well? > > The meta-qt5 layer doesn't seem to use this feature, but if it did, > would this device config files help to get an optimised Qt5 build > for TI SoCs? Especially, would that help to get OpenGL stuff sorted > out? > > Regards, > Chris > > [1] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ > [2] https://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-beagleboard-g++ Chris, Looking at those files shows very basic compiler optimization flags being set, -march, -mtune, -mfpu etc. I don't see any GL or GPU specifics in there. It also hardcodes things like soft-fp, which is not good. All this stuff is alredy taken care of by the build framework and I'm sure meta-qt5, like the old qt4, sets all the right COMPILER_FLAGS to get the most performance from the target CPU. -- Denys _______________________________________________ meta-ti mailing list meta-ti@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-ti ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qt5] mkspecs/devices: beagleboard == am335x ? 2013-07-27 2:20 ` Sundareson, Prabindh @ 2013-07-27 15:18 ` Christian Gagneraud 2013-07-27 3:41 ` Denys Dmytriyenko 0 siblings, 1 reply; 6+ messages in thread From: Christian Gagneraud @ 2013-07-27 15:18 UTC (permalink / raw) To: Sundareson, Prabindh; +Cc: meta-ti@yoctoproject.org 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? Regards, Chris [1] http://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-rasp-pi-g++ [2] http://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-imx6-g++ [3] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ [4] https://github.com/prabindh/meta-qt5/commit/c8129fb5057f9254c773f82d2fdbd85d9c56410a > > regards > Prabindh > ________________________________________ > From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of Dmytriyenko, Denys > Sent: Saturday, July 27, 2013 2:36 AM > To: Christian Gagneraud > Cc: meta-ti@yoctoproject.org > Subject: Re: [meta-ti] [Qt5] mkspecs/devices: beagleboard == am335x ? > > On Fri, Jul 26, 2013 at 10:45:02AM +1200, Christian Gagneraud wrote: >> Hi there, >> >> In qtbase sources, there are a couple of "device" definitions files, >> according to [1], this greatly help cross-compiling qt5. >> This device file specify things for CPU and GPU optimisations. So >> basically these files are tightly coupled with BSP providers. >> >> One of them is linux-beagleboard-g++ [2], is it appropriate to use >> this one for AM335x based platform as well? >> >> The meta-qt5 layer doesn't seem to use this feature, but if it did, >> would this device config files help to get an optimised Qt5 build >> for TI SoCs? Especially, would that help to get OpenGL stuff sorted >> out? >> >> Regards, >> Chris >> >> [1] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ >> [2] https://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-beagleboard-g++ > > Chris, > > Looking at those files shows very basic compiler optimization flags being set, > -march, -mtune, -mfpu etc. I don't see any GL or GPU specifics in there. It > also hardcodes things like soft-fp, which is not good. All this stuff is > alredy taken care of by the build framework and I'm sure meta-qt5, like the > old qt4, sets all the right COMPILER_FLAGS to get the most performance from > the target CPU. > > -- > Denys > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qt5] mkspecs/devices: beagleboard == am335x ? 2013-07-27 15:18 ` Christian Gagneraud @ 2013-07-27 3:41 ` Denys Dmytriyenko 2013-07-27 20:05 ` Christian Gagneraud 0 siblings, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2013-07-27 3:41 UTC (permalink / raw) To: Christian Gagneraud; +Cc: meta-ti@yoctoproject.org 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 -- Denys > [1] http://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-rasp-pi-g++ > [2] http://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-imx6-g++ > [3] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ > [4] https://github.com/prabindh/meta-qt5/commit/c8129fb5057f9254c773f82d2fdbd85d9c56410a > > > > > >regards > >Prabindh > >________________________________________ > >From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of Dmytriyenko, Denys > >Sent: Saturday, July 27, 2013 2:36 AM > >To: Christian Gagneraud > >Cc: meta-ti@yoctoproject.org > >Subject: Re: [meta-ti] [Qt5] mkspecs/devices: beagleboard == am335x ? > > > >On Fri, Jul 26, 2013 at 10:45:02AM +1200, Christian Gagneraud wrote: > >>Hi there, > >> > >>In qtbase sources, there are a couple of "device" definitions files, > >>according to [1], this greatly help cross-compiling qt5. > >>This device file specify things for CPU and GPU optimisations. So > >>basically these files are tightly coupled with BSP providers. > >> > >>One of them is linux-beagleboard-g++ [2], is it appropriate to use > >>this one for AM335x based platform as well? > >> > >>The meta-qt5 layer doesn't seem to use this feature, but if it did, > >>would this device config files help to get an optimised Qt5 build > >>for TI SoCs? Especially, would that help to get OpenGL stuff sorted > >>out? > >> > >>Regards, > >>Chris > >> > >>[1] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/ > >>[2] https://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-beagleboard-g++ > > > >Chris, > > > >Looking at those files shows very basic compiler optimization flags being set, > >-march, -mtune, -mfpu etc. I don't see any GL or GPU specifics in there. It > >also hardcodes things like soft-fp, which is not good. All this stuff is > >alredy taken care of by the build framework and I'm sure meta-qt5, like the > >old qt4, sets all the right COMPILER_FLAGS to get the most performance from > >the target CPU. > > > >-- > >Denys > >_______________________________________________ > >meta-ti mailing list > >meta-ti@yoctoproject.org > >https://lists.yoctoproject.org/listinfo/meta-ti > > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qt5] mkspecs/devices: beagleboard == am335x ? 2013-07-27 3:41 ` Denys Dmytriyenko @ 2013-07-27 20:05 ` Christian Gagneraud 0 siblings, 0 replies; 6+ messages in thread From: Christian Gagneraud @ 2013-07-27 20:05 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-ti@yoctoproject.org 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 > ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-07-27 8:05 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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.