# Missing prebuilds for IGT extensions for Preview Release 5.9

**URL:** <https://discourse.slicer.org/t/missing-prebuilds-for-igt-extensions-for-preview-release-5-9/44143>\
**Category:** Development\
**Tags:** slicerigt, openigtlink, extensions, preview\
**Created:** [August 20, 2025, 7:08am UTC](https://discourse.slicer.org/t/missing-prebuilds-for-igt-extensions-for-preview-release-5-9/44143 "2025-08-20T07:08:36Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ruffsl](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ruffsl/32/80858_2.png) [@ruffsl](https://discourse.slicer.org/u/ruffsl)\
**Post date:** [August 26, 2025, 4:48pm UTC](https://discourse.slicer.org/t/missing-prebuilds-for-igt-extensions-for-preview-release-5-9/44143/10 "2025-08-26T16:48:00Z")

</div>

> [@ruffsl](#):
>
> This all aside, it is concerning that the official Slicer build environment when used locally is not outputting an equivalent running binary as the remote buildfarm does.

In searching for resources on the missing `libCTKQtTesting.so` library, in found:

> [@Slicer-5.2.2-linux-amd64/Slicer does not launch](https://discourse.slicer.org/t/slicer-5-2-2-linux-amd64-slicer-does-not-launch/31318/4):
>
> Hi @tbillah - it looks like you didn’t run the ldd inside the shell launched by the Slicer launcher. Try this: ubuntu@sdp-console:/home/pieper$ cd ~/Downloads/Slicer-5.4.0-linux-amd64 ubuntu@sdp-console:~/Downloads/Slicer-5.4.0-linux-amd64$ ./Slicer --launch ldd bin/SlicerApp-real linux-vdso.so.1 (0x00007ffc31a93000) libqSlicerApp.so =\> /home/ubuntu/Downloads/Slicer-5.4.0-linux-amd64/bin/../lib/Slicer-5.4/libqSlicerApp.so (0x00007fc7d156e000) libqSlicerBaseQTApp.so =\> …

An sure enough, `libCTKQtTesting.so` was merely just the first shared lib not found:

```shell
~/t/S/S/Slicer-build> ./Slicer --launch ldd ./bin/SlicerApp-real | head
        linux-vdso.so.1 (0x0000773d3e11d000)
        libqSlicerApp.so => /home/ruffsl/tmp/Slicer-5.9/Slicer-build/Slicer-build/bin/./libqSlicerApp.so (0x0000773d3e073000)
        libqSlicerBaseQTApp.so => /home/ruffsl/tmp/Slicer-5.9/Slicer-build/Slicer-build/bin/./libqSlicerBaseQTApp.so (0x0000773d3e01f000)
        libqSlicerModulesCore.so => /home/ruffsl/tmp/Slicer-5.9/Slicer-build/Slicer-build/bin/./libqSlicerModulesCore.so (0x0000773d3dfff000)
        libqSlicerBaseQTCLI.so => /home/ruffsl/tmp/Slicer-5.9/Slicer-build/Slicer-build/bin/./libqSlicerBaseQTCLI.so (0x0000773d3df9d000)
        libqSlicerBaseQTGUI.so => /home/ruffsl/tmp/Slicer-5.9/Slicer-build/Slicer-build/bin/./libqSlicerBaseQTGUI.so (0x0000773d3dc00000)
        libqMRMLWidgets.so => /home/ruffsl/tmp/Slicer-5.9/Slicer-build/Slicer-build/bin/./libqMRMLWidgets.so (0x0000773d3d800000)
        libCTKQtTesting.so.0.1 => not found
        libCTKVisualizationVTKWidgets.so.0.1 => not found
        libCTKScriptingPythonWidgets.so.0.1 => not found

```

After downloading and inspecting the buildfarm artifacts for the same commit, noticed the file tree was different compared to my local cmake build folder, and that I was attempting to run the `Slicer` binary directly, rather than from the extracted launcher binary from the generated `.tar.gz` archive nested inside the very same local build.

Sure enough, the packaged version is working as expected without any missing libs:

```auto
~/t/S/S/Slicer-build/Slicer-5.9.0-2025-08-25-linux-amd64$ ./Slicer \
    --launch ldd ./bin/SlicerApp-real | grep "not found"
~/t/S/S/Slicer-build/Slicer-5.9.0-2025-08-25-linux-amd64$

```

Is this the Cmake macro triggered by this corresponding command? Cpack is new to me.

```auto
$slicer_build_env_script cmake --build Slicer-build/Slicer-build --target package

```

> <https://github.com/Slicer/Slicer/blob/284df9431ec0dd02db225494de9067898a6a43a4/CMake/SlicerPackageAndUploadTarget.cmake#L142-L146>

---

_[View the full topic](https://discourse.slicer.org/t/missing-prebuilds-for-igt-extensions-for-preview-release-5-9/44143)._