From: Quentin Schulz via buildroot <buildroot@buildroot.org>
To: Quentin Schulz <foss+buildroot@0leil.net>, buildroot@buildroot.org
Cc: Joshua Henderson <joshua.henderson@microchip.com>,
Bartosz Bilas <b.bilas@grinn-global.com>,
Peter Seiderer <ps.report@gmx.net>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [PATCH 2025.02.x 5/5] package/qt5: bump packages to latest 5.15 kde submodule version
Date: Fri, 27 Mar 2026 17:58:05 +0100 [thread overview]
Message-ID: <fcef4549-6961-4824-a4c7-a73552bf3bf9@cherry.de> (raw)
In-Reply-To: <20260324-qt5-5-15-18-2025-02-x-v1-5-9d25b343a6e3@cherry.de>
Hi all,
On 3/24/26 12:01 PM, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> Bump qt5 packages to latest submodule versions from
> https://invent.kde.org/qt/qt/qt5/-/tree/kde/5.15
>
> qtbase repo is a few commits after a tag named v5.15.18-lts-lgpl so
> assume it's now 5.15.18.
>
> qt5base patches are updated to make them apply silently and cleanly.
>
> For qt5webengine-chromium:
> - 0001-Add-python3-build-support.patc is removed as commit 68302c9ea158
> ("Enable building with Python 3") contains similar changes,
> - 0004-Migrate-presubmit-to-python3.patch is only partially kept as
> commit 68302c9ea158 ("Enable building with Python 3") contains similar
> changes,
> - 0006-Fix-build-in-Python-3.11-invalid-mode-rU.patch is only partially
> kept as commit 68302c9ea158 ("Enable building with Python 3") contains
> similar changes,
> - 0007-Replace-imp.load_source-with-importlib-equivalent.patch is
> removed as commit 68302c9ea158 ("Enable building with Python 3")
> contains similar changes,
> - 0010-Fix-building-with-system-libxml2.patch is removed as commit
> c98d28f2f0f2 ("Fix building with system libxml2") contains similar
> changes,
> - 0012-Include-cstdint-for-uintptr_t-uint8_t-etc.patch is renamed
> 0009-Include-cstdint-for-uintptr_t-uint8_t-etc.patch and contains more
> file patching to make qt5webengine build again,
>
> For qt5webengine:
> - 0002-Add-python3-build-support.patch is removed as commit 2294cc4ed5fd
> ("Add option to chose python version for building 5.15 WebEngine")
> contains similar changes. It now supports both Python2 and Python3 and
> defaults to Python2 if found first. This can be overridden with
> -webengine-python-version python3 in QT5WEBENGINE_CONF_OPTS but this
> was unnecessary in my tests as Python3 was properly selected from
> $(HOST_DIR)/bin/.
>
> qt5webengine-chromium is updated with qt5webengine following the logic
> stated in Buildroot commit c53455ea4ffa
> ("package/qt5/qt5webengine-chromium: bump version after qtwebengine
> bump").
>
> I am unsure whether qt5webengine-chromium-catapult also requires an
> update.
>
Note that I made a mistake in v1 of the series for master that I
necessarily made when backporting for 2025.02, see...
[...]
> diff --git a/package/qt5/qt5base/qt5base.mk b/package/qt5/qt5base/qt5base.mk
> index 3ad2bdfc04..0e375e83fe 100644
> --- a/package/qt5/qt5base/qt5base.mk
> +++ b/package/qt5/qt5base/qt5base.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -QT5BASE_VERSION = 2b9835f5c9bcfe3105b60a8dd33c1db7d8611378
> +QT5BASE_VERSION = bebdfd54917e25d1c100e6bd9f5dd53c2e645fd8
> QT5BASE_SITE = $(QT5_SITE)/qtbase
> QT5BASE_SITE_METHOD = git
> QT5BASE_CPE_ID_VENDOR = qt
... there should be a change to QT5BASE_CPE_ID_VERSION here too. See v2
here:
https://lore.kernel.org/buildroot/20260327-qt5-5-15-18-v2-5-4c98e853266a@cherry.de/.
I already didn't like much sending a backport series for 2025.02 before
the series for master was merged so I will refrain from posting a v2 for
the backport, but if the series for master gets merged, this one here
only needs
-QT5BASE_CPE_ID_VERSION = 5.15.14
+QT5BASE_CPE_ID_VERSION = 5.15.18
If you want to modify when applying without going through a v2.
Otherwise, lemme know I'll take care of the backport whenever possible.
Cheers,
Quentin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-27 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 11:01 [Buildroot] [PATCH 2025.02.x 0/5] package/qt5: misc fixes + bump to 5.15.18 Quentin Schulz via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 1/5] package/qt5/qt53d: disable assimp support when BR2_PACKAGE_ASSIMP is not set Quentin Schulz via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 2/5] package/qt5/qt53d: force using Buildroot's assimp when selected Quentin Schulz via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 3/5] package/qt5/qt53d: always disable assimp support Quentin Schulz via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 4/5] package/qt5/qt5webengine-chromium: fix zlib license hash Quentin Schulz via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 5/5] package/qt5: bump packages to latest 5.15 kde submodule version Quentin Schulz via buildroot
2026-03-27 16:58 ` Quentin Schulz via buildroot [this message]
2026-04-10 10:09 ` Thomas Perale via buildroot
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=fcef4549-6961-4824-a4c7-a73552bf3bf9@cherry.de \
--to=buildroot@buildroot.org \
--cc=b.bilas@grinn-global.com \
--cc=foss+buildroot@0leil.net \
--cc=giulio.benetti@benettiengineering.com \
--cc=joshua.henderson@microchip.com \
--cc=ps.report@gmx.net \
--cc=quentin.schulz@cherry.de \
--cc=thomas.petazzoni@bootlin.com \
/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