# Cmake cannot locate VTK, VTK installation incomplete, VTK and paraview conflict

**URL:** https://discourse.vtk.org/t/cmake-cannot-locate-vtk-vtk-installation-incomplete-vtk-and-paraview-conflict/15402
**Category:** Support
**Created:** [March 19, 2025, 11:14am UTC](https://discourse.vtk.org/t/cmake-cannot-locate-vtk-vtk-installation-incomplete-vtk-and-paraview-conflict/15402 "2025-03-19T11:14:44Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [March 19, 2025, 12:11pm UTC](https://discourse.vtk.org/t/cmake-cannot-locate-vtk-vtk-installation-incomplete-vtk-and-paraview-conflict/15402/2 "2025-03-19T12:11:34Z")

</div>

> [@AP76](#):
>
> There seems to be a conflict between paraview and vtk.

There is. They both provide the `vtk` Python module. ParaView installs its VTK configuration in a subdirectory of its own. There should be a `/usr/lib/*/cmake/paraview-*/vtk` path you can pass as `VTK_DIR` to use the VTK that comes with the ParaView package. You’ll need the `-dev` packages to provide these files.

---

_[View the full topic](https://discourse.vtk.org/t/cmake-cannot-locate-vtk-vtk-installation-incomplete-vtk-and-paraview-conflict/15402)._