From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt on AM3517EVM
Date: Tue, 17 Jul 2012 09:32:12 +0200 [thread overview]
Message-ID: <20120717093212.0c7d5415@skate> (raw)
In-Reply-To: <CALo-6+hhvCkfT_4Rz4POqw5j_BPPLKHZ0saqEyeiKsp-tSJLdA@mail.gmail.com>
Le Mon, 16 Jul 2012 10:40:23 -0700,
Charles Krinke <charles.krinke@gmail.com> a ?crit :
> First of all, +100 for Thomas, Arnout and Julian. This morning, I was
> able to load the jffs2 compiled file system from buildroot and run
> "ts_calibrate" and got a functioning touch screen and color LCD with
> Qt on the LogicPD AM3517EVM after *removing* the environment variable
> QMAKESPEC which the TI-SDK insisted on adding to my .bashrc.
Great.
> Of course, no sooner had I gotten it to work then my customer says
> "Thats cool, how about Qt5?"
>
> So, ... are we considering either a Qt5 bump or either Qt4/Qt5 with an
> xconfig option?
I think Qt5 needs a separate package from qt4, because many, many
things have changed in Qt5. Also Qt5 apparently requires an OpenGL
renderer, which wasn't the case in Qt4, so we will probably be keeping
Qt4 around for quite a while for low-end platforms.
Anyone willing to work on packaging Qt5 is definitely more than welcome
to contribute such effort.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-17 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 17:40 [Buildroot] Qt on AM3517EVM Charles Krinke
2012-07-17 7:32 ` Thomas Petazzoni [this message]
2012-07-17 13:44 ` Charles Krinke
2012-07-19 16:11 ` Julian Lunz
2012-07-19 16:32 ` Charles Krinke
2012-07-20 7:04 ` Yegor Yefremov
2012-07-24 15:54 ` Arnout Vandecappelle
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=20120717093212.0c7d5415@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox