From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Dylan Bespalko <dylan.bespalko@gmail.com>,
Roy Kollen Svendsen <roykollensvendsen@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: [Buildroot] [PATCH v4 0/3] package/python-pyside6: new package
Date: Mon, 16 Nov 2026 16:56:49 +0100 [thread overview]
Message-ID: <20261116155652.4181839-1-angelo.compagnucci@gmail.com> (raw)
In-Reply-To: <20240812080307.553359-1-dylan.bespalko@gmail.com>
Hello,
this series updates an older one: "added package/python-{shiboken6,
pyside6}: new packages" by Dylan Bespalko. Its last version was v3, sent
in August 2024 [1].
It adds PySide6, the Python bindings of Qt6, and Shiboken6, the
generator that builds them.
Dylan is still the author of the patches. I brought them up to date
with the current Buildroot and Qt6, and I added myself as co-author.
The main changes since v3:
- The single patch is now three: python-shiboken6, python-pyside6 and
the runtime test.
- The version goes from 6.7.2 to 6.11.3, the Qt6 version of Buildroot.
Qt for Python must have the same version as Qt6, so the packages move
to package/qt6/ and follow QT6_VERSION.
- The source is the release tarball, not the git repository.
- pyside-tools is not packaged. As Dylan proposed in his reply to v3,
the Qt tools "uic -g python" and "rcc -g python" do the same job.
v3 added a DEVELOPERS entry for Dylan. v4 does not: the packages are
now in package/qt6/, which already has maintainers, and the test files
are in my entry. Dylan, tell me if you want to be listed too.
Each patch lists its own changes below the "---" line.
This series replaces the v3 patch on patchwork [1], which can be marked
as superseded.
[1] https://patchwork.buildroot.org/project/buildroot/patch/20240812080307.553359-1-dylan.bespalko@gmail.com/
Best regards,
Angelo
Dylan Bespalko (3):
package/python-shiboken6: new package
package/python-pyside6: new package
support/testing: add python-pyside6 runtime test
DEVELOPERS | 2 +
package/qt6/Config.in | 2 +
package/qt6/python-pyside6/Config.in | 32 ++++
.../qt6/python-pyside6/python-pyside6.hash | 9 +
package/qt6/python-pyside6/python-pyside6.mk | 86 +++++++++
package/qt6/python-shiboken6/Config.in | 12 ++
.../python-shiboken6/python-shiboken6.hash | 9 +
.../qt6/python-shiboken6/python-shiboken6.mk | 57 ++++++
.../tests/package/sample_python_pyside6.py | 165 ++++++++++++++++++
.../tests/package/test_python_pyside6.py | 63 +++++++
10 files changed, 437 insertions(+)
create mode 100644 package/qt6/python-pyside6/Config.in
create mode 100644 package/qt6/python-pyside6/python-pyside6.hash
create mode 100644 package/qt6/python-pyside6/python-pyside6.mk
create mode 100644 package/qt6/python-shiboken6/Config.in
create mode 100644 package/qt6/python-shiboken6/python-shiboken6.hash
create mode 100644 package/qt6/python-shiboken6/python-shiboken6.mk
create mode 100644 support/testing/tests/package/sample_python_pyside6.py
create mode 100644 support/testing/tests/package/test_python_pyside6.py
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-11-16 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:03 [Buildroot] [PATCH v3 1/1] added package/python-{shiboken6, pyside6}: new packages Dylan Bespalko
2024-08-14 6:02 ` Dylan Bespalko
2026-11-16 15:56 ` Angelo Compagnucci [this message]
2026-11-16 15:56 ` [Buildroot] [PATCH v4 1/3] package/python-shiboken6: new package Angelo Compagnucci
2026-11-16 15:56 ` [Buildroot] [PATCH v4 2/3] package/python-pyside6: " Angelo Compagnucci
2026-11-16 15:56 ` [Buildroot] [PATCH v4 3/3] support/testing: add python-pyside6 runtime test Angelo Compagnucci
2026-11-16 21:29 ` [Buildroot] [PATCH v4 0/5] package/python-pyside6: new package Angelo Compagnucci
2026-11-16 21:29 ` [Buildroot] [PATCH v4 1/5] package/python-shiboken6: " Angelo Compagnucci
2026-11-16 21:29 ` [Buildroot] [PATCH v4 2/5] package/python-pyside6: " Angelo Compagnucci
2026-11-16 21:29 ` [Buildroot] [PATCH v4 3/5] support/testing: add python-pyside6 runtime test Angelo Compagnucci
2026-11-16 21:29 ` [Buildroot] [PATCH v4 4/5] package/python-matplotlib: add Qt6 support to the Qt display Angelo Compagnucci
2026-11-16 21:29 ` [Buildroot] [PATCH v4 5/5] support/testing: add python-matplotlib runtime test Angelo Compagnucci
2026-11-16 21:36 ` [Buildroot] [PATCH v5 0/5] package/python-pyside6: new package Angelo Compagnucci
2026-11-16 21:36 ` [Buildroot] [PATCH v5 1/5] package/python-shiboken6: " Angelo Compagnucci
2026-11-16 21:36 ` [Buildroot] [PATCH v5 2/5] package/python-pyside6: " Angelo Compagnucci
2026-11-16 21:36 ` [Buildroot] [PATCH v5 3/5] support/testing: add python-pyside6 runtime test Angelo Compagnucci
2026-11-16 21:36 ` [Buildroot] [PATCH v5 4/5] package/python-matplotlib: add Qt6 support to the Qt display Angelo Compagnucci
2026-11-16 21:36 ` [Buildroot] [PATCH v5 5/5] support/testing: add python-matplotlib runtime test Angelo Compagnucci
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=20261116155652.4181839-1-angelo.compagnucci@gmail.com \
--to=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.org \
--cc=dylan.bespalko@gmail.com \
--cc=roykollensvendsen@gmail.com \
--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