From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v4 1/3] package/qt5: bump version to 5.13.2
Date: Sat, 11 Apr 2020 15:01:47 +0200 [thread overview]
Message-ID: <20200411150147.4849dfe9@windsurf.home> (raw)
In-Reply-To: <20200403212357.26997-1-ps.report@gmx.net>
On Fri, 3 Apr 2020 23:23:55 +0200
Peter Seiderer <ps.report@gmx.net> wrote:
> qt5canvas3d:
> - removed with 5.13 according to [1]
>
> qt5webengine:
> - remove 0001-pkg_config-Fixes-when-use_sysroot-false.patch
> (taken from upstream [2])
> - update 3rdparty license hash list and chromium-latest.inc file
>
> [1] https://doc.qt.io/qt-5/whatsnew513.html
> [2] https://chromium.googlesource.com/chromium/src/+/a8c8396fd20d98666d517c45b358c63736e345ef
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> Changes v1 -> v2:
> - remove spurious qt5base commit log entry (leftover from some
> early draft, suggested by Thomas Petazzoni)
> - fix qt5scxml vs. qt5canvas3d typo, reword comment message and
> fix indent, remove unneeded license condition (suggested by
> Thomas Petazzoni)
I've added a Config.in.legacy entry for the removed qt5canvas3d option,
and then applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-11 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 21:23 [Buildroot] [RFC v4 1/3] package/qt5: bump version to 5.13.2 Peter Seiderer
2020-04-03 21:23 ` [Buildroot] [RFC v4 2/3] package/qt5: bump version to 5.14.2 Peter Seiderer
2020-04-11 13:01 ` Thomas Petazzoni
2020-04-03 21:23 ` [Buildroot] [RFC v4 3/3] package/qt5/qt5wayland: fix compile for rpi3 Peter Seiderer
2020-04-11 13:03 ` Thomas Petazzoni
2020-04-11 15:24 ` Peter Seiderer
2020-04-11 13:01 ` Thomas Petazzoni [this message]
2020-04-11 15:09 ` [Buildroot] [RFC v4 1/3] package/qt5: bump version to 5.13.2 Peter Seiderer
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=20200411150147.4849dfe9@windsurf.home \
--to=thomas.petazzoni@bootlin.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 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.