Details
-
Epic
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
PySide Cross Compilation
-
57866a57586d401c784f809f9f7994b0e4623706, 4b12b8f55 (dev), 2f70befc2 (6.5)
Description
Motivation
During the development of PySide 2, for 5.12+ versions, the main goal was to get rid of most of the flaws, and raise PySide's level so people could rely on the module both for just-for-fun and commercial projects.
After a couple of releases, the focus was moved forward Qt 6 compatibility, and with 6.0 out, and 6.1 almost around the corner, it makes sense to focus on the next steps for 6.2+.
Objective
The goal of this Epic is to improve the build infrastructure of PySide and Shiboken, to be able to cross compile the project for different targets, focusing mainly on embedded systems with ARM and aarch64 architectures. The decision of the architectures comes from the many requests specifically for Raspberry Pi devices, and also linux-based aarch64 devices like the Pinebook, and Pinephone.
Next steps
- Re-structure the cmake configuration to build libshiboken, and shiboken gen, so the tools can be build for the host and target, using the host binary for the cross compilation of the target, and the target binaries for distribution.
- It's important to notice that when building shiboken, the process follows the order: ApiExtractor, libshiboken, Shiboken generator, and Shiboken Module (Python).
- Shiboken generator, depends on both ApiExtractor
- Shiboken module (Python), depends on libshiboken
- Introduce command lines options related to this process for the setup.py build method, so it's easy to package and distribute.
Background
This task was raised before by azarubkin, but was later transform into an EPIC:
There is https://www.piwheels.org/ site which aims to provide wheels for Python packages built for Raspberry Pi. Unfortunately, there is no PySide2 package there.
As the maintainer of the site said (https://github.com/bennuttall/piwheels/issues/84), he needs either source package (.tar.gz) to build the wheel from, or ready wheel prebuilt by you.
It would be great to see PySide2 supported by Raspberry Pi!
Attachments
Issue Links
- covers
-
PYSIDE-2058 Unable to build PySide6.2.4 for Raspbian Bullseye
- Closed
- depends on
-
PYSIDE-1033 Improve the shiboken build process
- Closed
-
QTBUG-90843 B2Qt61: Raspberry Pi 4 (ARM-v8A 64bit) with Yocto 3.2 Gatesgarth (not a refe)
- Closed
-
QTBUG-86955 Raspberry Pi 4 (ARM-v8A-32/64bit) with Debian based Raspberry Pi OS and Qt apps
- Blocked
- is duplicated by
-
PYSIDE-853 Research Qt for Python Usage on Embedded Linux
- Withdrawn
- is required for
-
QTBUG-87045 Qt 6.2 hosts - macOS on ARM64 (moA)
- Closed
-
QTBUG-85279 Qt for macOS on Apple Silicon (arm64)
- Closed
- relates to
-
PYSIDE-1120 Support Qt for Python on MCU
- Open
-
PYSIDE-1477 shiboken2: fails on crossbuild, need to pass platform's target definition to clang
- Reported
-
PYSIDE-1837 Failed to install on Raspbian
- Closed
-
PYSIDE-2090 build shiboken generator when cross-compiling
- Closed
-
PYSIDE-1958 Cross-compilation fails
- Closed
-
PYSIDE-2057 shiboken2 stores compiler value at compile time
- Closed
-
PYSIDE-1439 Document how to build LibClang from source
- Closed
-
PYSIDE-1592 we want to develop android app using pyside6 and qt
- Closed
- resulted in
-
PYSIDE-1810 Write documentation on how to cross-build Qt For Python
- Closed
-
PYSIDE-1812 Allow specifying target sysroot for header extraction when cross-compiling
- Open
-
PYSIDE-1811 Replace cross-building manylinux2014 tag with proper glibc version detection
- Open
- mentioned in
-
Page Loading...
For Gerrit Dashboard: PYSIDE-802 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
443467,1 | build_scripts: Don't use Qt from the environment for configure checks | dev | pyside/pyside-setup | Status: NEW | +1 | 0 |