queue: shiboken6 -> ci-running (PR #1696); note toolchain findings for pyside6-essentials

Author: luhenry

.queue.yml

@@ -733,7 +733,7 @@ packages:
   repo: https://code.qt.io/cgit/pyside/pyside-setup.git/
   status: queued
   pr: null
-  notes: '2 Linux wheels upstream (abi: cp310); no riscv64 on PyPI or pypi.riseproject.dev.'
+  notes: '2 Linux wheels upstream (abi: cp310); no riscv64 on PyPI or pypi.riseproject.dev. Depends on shiboken6 being available first (runtime requires-dist, and pyside6-essentials own build self-generates its bindings against an installed shiboken6-generator the same way shiboken6 does). shiboken6 6.11.2 riscv64 port is in progress (PR #1696, see that entry) - not merged/published yet. Key finding for whoever picks up pyside6-essentials/pyside6/pyside6-addons: the libclang dependency is NOT libclang-scale (unlike build-libclang.yml, PR #866, ~10h from-source LLVM/Clang compile) - Rocky 10 riscv64s AppStream repo (manylinux_2_39_riscv64 base) ships prebuilt clang-devel/llvm-devel 21.1.8 (ClangConfig.cmake/LLVMConfig.cmake/libclang.so/headers) AND qt6-qtbase-devel (Qt6Config.cmake/qtpaths6) - both installable via a plain `dnf install`, confirmed against the real repodata at dl.rockylinux.org. pyside6-essentials/pyside6/pyside6-addons will need the FULL Qt6 module set they bind (qt6-qt5compat, qt6-qtdeclarative, qt6-qtsvg, etc. - check which are in AppStream vs CRB-only per module before assuming coverage), not just qtbase, and will additionally need shiboken6-generator installed (build it the same way build-shiboken6.yml does, or wait for it to be published once shiboken6 is scoped in). Do not attempt until shiboken6 is merged and published.'
 - pkg: pycocotools
   version: 2.0.11
   home: https://github.com/ppwwyyxx/cocoapi
@@ -745,9 +745,9 @@ packages:
   version: 6.11.2
   home: https://pyside.org
   repo: https://code.qt.io/cgit/pyside/pyside-setup.git/
-  status: queued
-  pr: null
-  notes: '2 Linux wheels upstream (abi: cp310); no riscv64 on PyPI or pypi.riseproject.dev.'
+  status: ci-running
+  pr: https://github.com/riseproject-dev/python-wheels/pull/1696
+  notes: '2 Linux wheels upstream (abi: cp310-abi3); no riscv64 on PyPI or pypi.riseproject.dev. No sdist on PyPI (pyside-setup has no per-component sdist); build-from-checkout of pyside/pyside-setup at git tag 6.11.2 via its own setup.py (not PEP517/cibuildwheel-compatible - custom --build-type flag), docker-run-yourself shape like build-libclang.yml. Initial concern was that ApiExtractor (shiboken6-generators C++ parser) needs libclang, expected to require the same from-scratch multi-hour LLVM/Clang compile as build-libclang.yml (PR #866, ~10h). Not the case here: Rocky 10 riscv64s AppStream repo (the manylinux_2_39_riscv64 base) already ships prebuilt clang-devel/llvm-devel 21.1.8 with ClangConfig.cmake/LLVMConfig.cmake/libclang.so/headers (confirmed via the real repodata at dl.rockylinux.org, no container needed) - setup_clang()s find_package(Clang CONFIG REQUIRED) finds it with no LLVM_INSTALL_DIR override needed. Second dependency, also unexpected: sources/shiboken6/cmake/ShibokenSetup.cmake does find_package(Qt6 REQUIRED COMPONENTS Core) even for a shiboken6-only (non-PySide) build - also covered by Rocky 10 AppStream (qt6-qtbase-devel, confirmed in the same repodata, includes qtpaths6 and Qt6Config.cmake). Third wrinkle: shiboken6s own bindings (shibokenmodule) are self-generated - shibokenmodule/CMakeLists.txt runs the already-built Shiboken6::shiboken6 tool against typesystem_shiboken.xml, so shiboken6-generator (the 49-56MB wheel that bundles libclang.so, confirmed via requires_dist/wheel sizes on PyPI) has to be built and pip-installed into the build venv first, even though it is never published (out of scope per this tasks brief; see pyside6-essentials note below for what a future generator/pyside6 port would reuse). The final shiboken6 wheel (libshiboken.so + Shiboken*.so, ~270KB on aarch64) links only libpython - no Qt/Clang/GPL code ships in it, so no gpl_sources job. Worktree at .claude/worktrees/shiboken6, branch shiboken6. PR #1696 opened, CI just started (first run registers the workflow via pull_request). Not yet watched to completion - the dnf install list, the exact --build-type=shiboken6-generator/shiboken6 CLI flags (--qtpaths/--cmake/--limited-api=yes/--plat-name), and the auditwheel repair step are a first-pass best effort from reading the real pyside-setup source (main.py/options.py/config.py/the CMakeLists tree at tag 6.11.2), not yet CI-validated.'
 - pkg: bitstruct
   version: 8.23.0
   home: https://github.com/eerimoq/bitstruct