# SlicerVMTK is not being built for preview

**URL:** https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647
**Category:** Support
**Created:** [April 3, 2026, 4:43pm UTC](https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647 "2026-04-03T16:43:33Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [April 3, 2026, 4:43pm UTC](https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647/1 "2026-04-03T16:43:34Z")

</div>

SlicerVMTK fails to build on [cdash](https://slicer.cdash.org/builds/4168673/build) since a few weeks. The reported errors hint towards an environment problem on the build machines. It builds fine on Arch. Thanks for having a look.

---

<div class="post-metadata">

### Author: ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [April 3, 2026, 5:39pm UTC](https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647/2 "2026-04-03T17:39:39Z")

</div>

It actually appears like errors about not being compatible with VTK 9.6. When building on Arch did you use VTK 9.6?

See the following for updating details:

> <https://github.com/Slicer/Slicer/pull/8928#issuecomment-4074903898>
>
> Slicer extension compatibility based on https://github.com/Slicer/Slicer/commit/…cf471ffd35bd45705a15557001db1aa9e7d263e4:
> \- \[x\] https://github.com/lassoan/SlicerSegmentEditorExtraEffects/pull/69
> \- \[x\] https://github.com/IGSIO/IGSIO/pull/44
> \- \[x\] https://github.com/IGSIO/SlicerIGSIO/pull/33

---

<div class="post-metadata">

### Author: ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [April 3, 2026, 6:19pm UTC](https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647/3 "2026-04-03T18:19:26Z")

</div>

At 1b21266bf47, Slicer built with VTK 9.5.

I’ll try a clean build next time. Thanks.

---

<div class="post-metadata">

### Author: ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [April 3, 2026, 9:21pm UTC](https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647/4 "2026-04-03T21:21:13Z")

</div>

A clean build of Slicer used VTK 9.6.

SlicerVMTK could be built after fixing the \<iostream\> includes, both in VMTK itself and in the C++ modules of SlicerVMTK.

I’ll send a PR in both projects ASAP.

---

<div class="post-metadata">

### Author: ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [April 4, 2026, 9:20am UTC](https://discourse.slicer.org/t/slicervmtk-is-not-being-built-for-preview/46647/5 "2026-04-04T09:20:10Z")

</div>

A [PR](https://github.com/vmtk/vmtk/pull/481) is submitted for the VMTK libraries. If it gets merged, I’ll proceed with updating SlicerVMTK.
