From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Currently packaging Qt5
Date: Mon, 14 Jan 2013 12:45:21 +0100 [thread overview]
Message-ID: <20130114124521.1671c93e@skate> (raw)
In-Reply-To: <50F3EDF8.6010203@lucaceresoli.net>
Luca,
On Mon, 14 Jan 2013 12:37:28 +0100, Luca Ceresoli wrote:
> Are you going to leave the option in BR to use the old QT4?
Yes, I packaging Qt5 as a completely separate package from Qt4.
In fact, I'm even packaging it as multiple separate packages, because
they now provide split tarballs for various components of the Qt5
stack, which is great.
> I think it would be useful, mostly for boards having no OGLES
> acceleration, as well as to avoid any backward compatibility issues
> for old application code.
Of course. Note however that Qt5 doesn't require OpenGLES. There are
linuxfb and directfb backend that normally work with OpenGLES.
However, the linuxfb backend is crashing at the moment. I've already
sent one (easy) fix to the Qt guys, and reported the next crash.
They suggested some thing that didn't work, I'm still waiting for some
news.
So basically, the stuff will compile, I can build and run a basic QtCore
application, but there will be some work to runtime test all the
combinations of graphical backends and so on. I will not be testing
everything.
Best regards,
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:[~2013-01-14 11:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 9:58 [Buildroot] Currently packaging Qt5 Thomas Petazzoni
2013-01-14 10:50 ` Daniel Nyström
2013-01-14 11:04 ` Thomas Petazzoni
2013-02-19 4:18 ` prabindh
2013-02-19 15:29 ` Thomas Petazzoni
2013-05-20 3:31 ` prabindh
2013-05-22 11:55 ` Sundareson, Prabindh
2013-05-22 12:17 ` Thomas Petazzoni
2013-05-22 12:23 ` prabindh
2013-05-22 12:31 ` Thomas Petazzoni
2013-05-22 12:36 ` prabindh
2013-05-22 13:06 ` Thomas Petazzoni
2013-05-22 13:26 ` Sundareson, Prabindh
2013-05-22 13:30 ` Thomas Petazzoni
2013-05-22 13:35 ` prabindh
2013-05-22 14:04 ` Thomas Petazzoni
2013-05-22 14:18 ` Spenser Gilliland
2013-05-22 14:39 ` Thomas Petazzoni
2013-05-22 15:57 ` prabindh
2013-05-22 17:33 ` Spenser Gilliland
2013-05-23 20:38 ` Wojciech Sleńska
2013-05-22 12:16 ` Thomas Petazzoni
2013-05-22 12:21 ` prabindh
2013-01-14 11:37 ` Luca Ceresoli
2013-01-14 11:45 ` Thomas Petazzoni [this message]
2013-01-14 12:48 ` Sagaert Johan
2013-01-14 13:10 ` Thomas Petazzoni
2013-01-17 9:03 ` Arnout Vandecappelle
2013-02-06 9:56 ` Daniel Nyström
2013-02-06 10:04 ` Thomas Petazzoni
2013-02-06 10:12 ` Frédéric COIFFIER
2013-02-06 10:43 ` Thomas Petazzoni
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=20130114124521.1671c93e@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