# SlicerVMTK not building for SlicerPreview on cdash

**URL:** <https://discourse.slicer.org/t/slicervmtk-not-building-for-slicerpreview-on-cdash/42605>\
**Category:** VMTK\
**Created:** [April 17, 2025, 5:11pm UTC](https://discourse.slicer.org/t/slicervmtk-not-building-for-slicerpreview-on-cdash/42605 "2025-04-17T17:11:08Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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 18, 2025, 2:37pm UTC](https://discourse.slicer.org/t/slicervmtk-not-building-for-slicerpreview-on-cdash/42605/7 "2025-04-18T14:37:56Z")

</div>

I built VMTK at [6c189dd6](https://github.com/vmtk/vmtk/commit/6c189dd6ee644a466498bd382b0c19229f20daa5) with the following errors:

```auto
CMake Error at /home/arc/src/SlicerExtension-VMTK-SuperBuild9/VMTK-build/CMake/vtkWrapPython.cmake:209 (find_package):
  By not providing "FindPythonLibs.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "PythonLibs", but CMake did not find one.

```

If the changes in CMakeLists introduced by that commit are reverted, VMTK builds fine. Then SlicerVMTK can be built in turn.

This commit ([6c189dd6](https://github.com/vmtk/vmtk/commit/6c189dd6ee644a466498bd382b0c19229f20daa5)) probably needs the python changes it is expecting and they do not seem to be compatible with Slicer python.

It looks like there _might_ be a need for a SlicerPreview specific branch in the VMTK repository. It won’t be an easy task to maintain SlicerVMTK otherwise.

Or may be there’s some simpler solution.

---

_[View the full topic](https://discourse.slicer.org/t/slicervmtk-not-building-for-slicerpreview-on-cdash/42605)._