From: Christian Gagneraud <chgans@gna.org>
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Qt/TI question
Date: Fri, 16 Aug 2013 13:59:15 +1200 [thread overview]
Message-ID: <520D8773.1050307@gna.org> (raw)
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
next reply other threads:[~2013-08-16 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 1:59 Christian Gagneraud [this message]
2013-08-16 2:37 ` Qt/TI question Sundareson, Prabindh
2013-08-16 4:34 ` Christian Gagneraud
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=520D8773.1050307@gna.org \
--to=chgans@gna.org \
--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.