From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qt5: version bump
Date: Sun, 22 Dec 2013 18:50:07 +0100 [thread overview]
Message-ID: <20131222185007.590a5af4@skate> (raw)
In-Reply-To: <20131219153646.2EE009C0F1@busybox.osuosl.org>
Vincente,
On Thu, 19 Dec 2013 16:33:47 +0100, Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=e4a839277f7d74104e25fb4fd846f9c2bf3f9c1e
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> -bump version to 5.2.0
> -remove unneeded patches
> -remove invalid configure options
>
> [Peter: uclibc-no-lfs + qatomic patches still needed, new patch for uClibc]
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit broke the build of qt5jsbackend, because it no longer
exists in Qt 5.2 apparently. See:
http://autobuild.buildroot.org/results/d39/d399c08380c1713474cc9d9822af5f396b7d2ab6/build-end.log
http://download.qt-project.org/official_releases/qt/5.2/5.2.0/submodules/
According to
http://blog.qt.digia.com/blog/2013/09/30/qt-5-2-alpha-available/:
"""
The QML engine has undergone some intensive work over the last 9
months, and the first results can be seen in Qt 5.2. Qt Qml is now
using its own built-in Javascript engine and does not depend on V8
anymore. As such the QtJSBackend shared library has disappeared.
"""
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-12-22 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 15:33 [Buildroot] [git commit] qt5: version bump Peter Korsgaard
2013-12-22 17:50 ` Thomas Petazzoni [this message]
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=20131222185007.590a5af4@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