Qt/TI question

Qt/TI question

[Christian Gagneraud]

Hi there,

This is a bot off-topic, so if you know a better mailing list for this 
kind of things, please let me know.

I'm thinking about making a request on the qt-devel mailing list, and of 
course I am willing to provide work to get this feature working.

Qt comes with a list of supported devices [1], of which are the 
beagleboard and the pandaboard. It would be nice to have as well the 
beaglebone. A simple first step would be to add a mkspecs to the 
qt-platform-mkspec project [2].

Up to know, this is all off-topic, but:
The mkspecs simply specify compiler flags (C, CPP and LD) and point to a 
cross-toolchain. [3] is the example for omap3430.
I don't know who wrote that one, but it refers to a "beagle-narc-rootfs" 
and a Code Sourcery "arm-2010q1" (I assume it is CS because of the "q1" 
part).

And that's where meta-ti/arago could step in, because it is a 
toolchain/rootfs provider for TI SoCs.

Right now, I'm trying to build arago/dylan SDK with gles support. If it 
works, then the generated SDK could be used to allow building Qt4/5 out 
of yocto via the qt-platform-mkspecs.

Once this is showed to be working, a pull request could be made to 
qt-platform-mkspecs, and start a discussion on having the beaglebone 
added to the list of supported device and add a page on qt-project wiki 
a bit like the one for the beagleboard[4].

Any thoughts or suggestions?

Chris

[1] http://qt-project.org/wiki/Category:Devices
[2] http://gitorious.org/qt-platform-mkspecs
[3] 
http://gitorious.org/qt-platform-mkspecs/qt-platform-mkspecs/blobs/master/5.0/linux-omap3430-g++/qmake.conf
[4] http://qt-project.org/wiki/TIBeagleBoard

Re: Qt/TI question

[Sundareson, Prabindh]

Yes - that would be the goal, and we can review the patches as well.

The meta-qt5 recipes will also be changed, so ensure they are copied in the discussions,

regards,
Prabu


-----Original Message-----
From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Christian Gagneraud
Sent: Friday, August 16, 2013 7:29 AM
To: meta-ti@yoctoproject.org
Subject: [meta-ti] Qt/TI question

Hi there,

This is a bot off-topic, so if you know a better mailing list for this kind of things, please let me know.

I'm thinking about making a request on the qt-devel mailing list, and of course I am willing to provide work to get this feature working.

Qt comes with a list of supported devices [1], of which are the beagleboard and the pandaboard. It would be nice to have as well the beaglebone. A simple first step would be to add a mkspecs to the qt-platform-mkspec project [2].

Up to know, this is all off-topic, but:
The mkspecs simply specify compiler flags (C, CPP and LD) and point to a cross-toolchain. [3] is the example for omap3430.
I don't know who wrote that one, but it refers to a "beagle-narc-rootfs" 
and a Code Sourcery "arm-2010q1" (I assume it is CS because of the "q1" 
part).

And that's where meta-ti/arago could step in, because it is a toolchain/rootfs provider for TI SoCs.

Right now, I'm trying to build arago/dylan SDK with gles support. If it works, then the generated SDK could be used to allow building Qt4/5 out of yocto via the qt-platform-mkspecs.

Once this is showed to be working, a pull request could be made to qt-platform-mkspecs, and start a discussion on having the beaglebone added to the list of supported device and add a page on qt-project wiki a bit like the one for the beagleboard[4].

Any thoughts or suggestions?

Chris

[1] http://qt-project.org/wiki/Category:Devices
[2] http://gitorious.org/qt-platform-mkspecs
[3]
http://gitorious.org/qt-platform-mkspecs/qt-platform-mkspecs/blobs/master/5.0/linux-omap3430-g++/qmake.conf
[4] http://qt-project.org/wiki/TIBeagleBoard
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: Qt/TI question

[Christian Gagneraud]

On 16/08/13 14:37, Sundareson, Prabindh wrote:
> Yes - that would be the goal, and we can review the patches as well.
>
> The meta-qt5 recipes will also be changed, so ensure they are copied in the discussions,

Hi Prabu,

To start with, I was thinking to keep meta-qt5 aside, I have expressed 
my personal opinion about meta-qt5 before [1], basically I expressed the 
feeling that meta-qt5 try to adapt Qt to OE, instead of the other way 
around, currently qtbase needs 19 patches, of which lot of heavy 
modification to the Qt build process. Again this is my personal opinion, 
and i don't have materials yet to support my point.

Once the beaglebone page has been created on qt-project, it could be 
used to show that the best approach is to provide machine/SoC optimised 
mkspec and try not to patch Qt5 so heavily.

As well, I started to work on a yocto plugin for QtCreator, I'm using 
the Android and the BlackBerry/QNX plugins as references, but I am still 
at a very early stage:
Right now, it's just parsing the env and version files and provide a 
QtCreator GnuToolchain, the road is very long, I have next to provide a 
GdbSomething, a QtVersionSomething, a DeployOnTheTargetStuff, a 
KitThingy and many other classes.

The problem right now with the env script and the generically named 
mkspec is that to be able to configure QtCreator to use a yocto SDK, you 
have to source a file and run qtcreator form there, and then only you 
can configure it step by step and finally be able to build a project. 
This way of doing specialises your qtcreator session (not talking about 
the step by step configuration, just0 the build).
I never managed to build a project for different Yocto SDK without 
having to quit QtCreator, source another env file and run QtCreator again...

Anyway, I'm very open on the best approach with meta-qt5.

Last thing, please note as well, that I don't have much time to spend on 
this (read: these days at work), but I'm working on getting N weeks 
full-time, will see how high is the N! :)

[1] https://lists.yoctoproject.org/pipermail/meta-ti/2013-July/003092.html


>
> regards,
> Prabu
>
>
> -----Original Message-----
> From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Christian Gagneraud
> Sent: Friday, August 16, 2013 7:29 AM
> To: meta-ti@yoctoproject.org
> Subject: [meta-ti] Qt/TI question
>
> Hi there,
>
> This is a bot off-topic, so if you know a better mailing list for this kind of things, please let me know.
>
> I'm thinking about making a request on the qt-devel mailing list, and of course I am willing to provide work to get this feature working.
>
> Qt comes with a list of supported devices [1], of which are the beagleboard and the pandaboard. It would be nice to have as well the beaglebone. A simple first step would be to add a mkspecs to the qt-platform-mkspec project [2].
>
> Up to know, this is all off-topic, but:
> The mkspecs simply specify compiler flags (C, CPP and LD) and point to a cross-toolchain. [3] is the example for omap3430.
> I don't know who wrote that one, but it refers to a "beagle-narc-rootfs"
> and a Code Sourcery "arm-2010q1" (I assume it is CS because of the "q1"
> part).
>
> And that's where meta-ti/arago could step in, because it is a toolchain/rootfs provider for TI SoCs.
>
> Right now, I'm trying to build arago/dylan SDK with gles support. If it works, then the generated SDK could be used to allow building Qt4/5 out of yocto via the qt-platform-mkspecs.
>
> Once this is showed to be working, a pull request could be made to qt-platform-mkspecs, and start a discussion on having the beaglebone added to the list of supported device and add a page on qt-project wiki a bit like the one for the beagleboard[4].
>
> Any thoughts or suggestions?
>
> Chris
>
> [1] http://qt-project.org/wiki/Category:Devices
> [2] http://gitorious.org/qt-platform-mkspecs
> [3]
> http://gitorious.org/qt-platform-mkspecs/qt-platform-mkspecs/blobs/master/5.0/linux-omap3430-g++/qmake.conf
> [4] http://qt-project.org/wiki/TIBeagleBoard
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>