Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
6.2.4
-
None
-
Debian unstable
-
Linux/X11
Description
When building the code with CMake:
[ 31%] Built target QtCore PySide6/__init__.py: Unable to import Shiboken from /home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/build/sources/pyside6, /home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/build/sources/shiboken6, / home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/sources/pyside6/PySide6/support, /usr/lib/python310.zip, /usr/lib/python3.10, /usr/lib/python3.10/lib-dynload, /home/lisandro/.local/lib/python3.10/site-packages, /usr/l ocal/lib/python3.10/dist-packages, /usr/lib/python3/dist-packages Traceback (most recent call last): File "/home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/sources/pyside6/PySide6/QtCore/../support/generate_pyi.py", line 130, in <module> generate_all_pyi(outpath, options=options) File "/home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/sources/pyside6/PySide6/QtCore/../support/generate_pyi.py", line 72, in generate_all_pyi import PySide6 File "/home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/build/sources/pyside6/PySide6/__init__.py", line 111, in <module> _setupQtDirectories() File "/home/lisandro/damian/ics/repos/qt6_packaging/tqtc/pyside6/pyside6/build/sources/pyside6/PySide6/__init__.py", line 60, in _setupQtDirectories from shiboken6 import Shiboken ModuleNotFoundError: No module named 'shiboken6' make[2]: *** [sources/pyside6/PySide6/QtCore/CMakeFiles/QtCore_pyi.dir/build.make:70: sources/pyside6/PySide6/QtCore/CMakeFiles/QtCore_pyi] Error 1 make[1]: *** [CMakeFiles/Makefile2:5308: sources/pyside6/PySide6/QtCore/CMakeFiles/QtCore_pyi.dir/all] Error 2 make: *** [Makefile:136: all] Error 2
Like if the code needed to find shiboken in path. This can be avoided by commenting out lines 210 to 214 of sources/pyside6/cmake/Macros/PySideModules.cmake, ie, avoiding building the _pyi files.
Looking at the Arch's packaging on lines 38 to 51 the maintainer seems to override this by installing egg-info into /usr/local, which is not a suitable fix for packaging (my intention here is packaging pyside for a distro), as the build should not be installing anything on the build chroot.