No linux preview build since 4/22

muratmaga · May 1, 2026, 3:59pm

I just downloaded the latest preview for Linux and it is dated 4/22.

ebrahim · May 1, 2026, 4:45pm

Yes I think there are recent some issues being worked on (not by me)

Comment by Sunderlandkyl - BUG: Guard null SegmentationNode in qMRMLSegmentEditorWidget

main ← Sunderlandkyl:seg_edit_no_segmentation_effect_crash

Seems there is a failure on the nightly Linux build that is causing the CI to fa…il: ``` CMake Error at /usr/src/Slicer-build/Slicer-build/CMake/LastConfigureStep/cmake_install.cmake:1117 (file): file INSTALL cannot find "/usr/src/Slicer-build/CTK-build/CMakeExternals/Install/lib/libQtTesting.so": No such file or directory. Call Stack (most recent call first): /usr/src/Slicer-build/Slicer-build/cmake_install.cmake:162 (include) /opt/rh/gcc-toolset-14/root/usr/bin/strip: '/usr/src/Slicer-build/Slicer-build/_CPack_Packages/linux-amd64/TGZ/Slicer-5.11.0-2026-04-30-linux-amd64/./lib/Slicer-5.11/libQtTesting.so': No such file CPack Error: Error when generating package: Slicer ``` Linux nightly CDash failure: https://slicer.cdash.org/builds/4205217/build

github.com/Slicer/Slicer

BUG: Resolve QtTesting install library name from imported target (#9137)

main ← hjmjohnson:fix-qttesting-install-name

opened 05:56PM - 30 Apr 26 UTC

hjmjohnson

+67 -5

Fixes #9135. The CTK QtTesting tag bump (`cf5fa41…`, "ctk-2026-03-27 Qt5+Qt6 sup…port") renamed the shared library output from `QtTesting` to `qttesting`, causing nightly Linux packaging to fail. This change queries the actual library file name from the imported `qttesting` CMake target instead of hard-coding it, so future renames don't silently break packaging. <details> <summary>Root cause</summary> `CMake/SlicerBlockInstallQtTesting.cmake` hard-coded `libQtTesting.so` / `libQtTesting.dylib` / `QtTesting.dll`. After the CTK tag bump, CTK installs `libqttesting.so` (lowercase), so the install step errors: ``` file INSTALL cannot find /usr/src/Slicer-build/CTK-build/CMakeExternals/Install/lib/libQtTesting.so ``` </details> <details> <summary>Fix details</summary> - `find_package(QtTesting CONFIG REQUIRED)` to load the imported target. - Probe target names (`qttesting`, `QtTesting`, `QtTesting::qttesting`, `CTK::QtTesting`) so a future namespaced rename fails loudly instead of silently. - Resolve the library basename from `IMPORTED_LOCATION_<CONFIG>` (with fallbacks across known config types and `IMPORTED_LOCATION`). - Use that basename for both `install(FILES …)` and `slicerStripInstalledLibrary(…)`. - Documents a known limitation: assumes a single unversioned shared library file (no `libqttesting.so.1` SONAME chain). If upstream introduces SONAME versioning later, the block needs to install the symlink chain too — a comment in the file flags this. Verified locally: the generated `cmake_install.cmake` now references `libqttesting.so` from the actual CTK install tree. </details> ## Test plan - [ ] Linux nightly package build (CDash) succeeds: previously failing `cmake_install.cmake:1117` step now installs `libqttesting.so`. - [ ] macOS package contains `libqttesting.dylib`. - [ ] Windows package contains `qttesting.dll`.

Topic		Replies	Views
Missing qt library references Support build	1	669	June 1, 2020
Is there an issue with Linux builds currently? Support	13	162	July 22, 2025
Build failing in CTK on MacOS 10.12, Slicer nightly, Qt 5.9 Development build	23	2059	April 13, 2018
Build failure windows Development	36	3468	July 28, 2019
FYI : small patch to build Slicer on Arch Linux Development	3	285	June 20, 2022

No linux preview build since 4/22

Related topics