# Compiling headless ParaView with OSMesa

**URL:** https://discourse.paraview.org/t/compiling-headless-paraview-with-osmesa/8377
**Category:** ParaView Support
**Created:** [November 11, 2021, 4:06pm UTC](https://discourse.paraview.org/t/compiling-headless-paraview-with-osmesa/8377 "2021-11-11T16:06:26Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![robertsawko](https://discourse.paraview.org/user_avatar/discourse.paraview.org/robertsawko/32/6283_2.png) [@robertsawko](https://discourse.paraview.org/u/robertsawko)
#### Post date: [November 26, 2021, 3:54pm UTC](https://discourse.paraview.org/t/compiling-headless-paraview-with-osmesa/8377/13 "2021-11-26T15:54:19Z")

</div>

Setting `ENABLE_paraviewsdk` worked for PV and VTK, but I am sorry, I fear that only generated more questions…

1. Is it possible get headers of all the packages to be also installed under current configuration? Currently a CMake of my Catalyst adaptopr is failing because it cannot find OSMesa headers which are not installed on this machine.
2. Do I need to set CMAKE\_PREFIX\_PATH or CMAKE\_MODULE\_PATH and I do need to cover each subdirectory?
3. What does `DSUPERBUILD_DEBUG_CONFIGURE_STEPS=ON` do?

Here’s my current invocation.

```bash
cmake \
    -DCMAKE_BUILD_TYPE_paraview=RelWithDebInfo \
    -DPARAVIEW_BUILD_EDITION=CANONICAL \
    -DSUPERBUILD_OFFLINE_BUILD=ON \
    -DENABLE_python3=ON \
    -DENABLE_mpi=ON \
    -DUSE_SYSTEM_mpi=ON \
    -DENABLE_osmesa=ON \
    -DENABLE_llvm=ON \
    -DENABLE_paraviewsdk=ON \
    -DSUPERBUILD_DEBUG_CONFIGURE_STEPS=ON \
    -DCMAKE_INSTALL_PREFIX=$INSTALL_DIR \
    ../paraview-superbuild \
    && make download-all \
    && make install

```

---

_[View the full topic](https://discourse.paraview.org/t/compiling-headless-paraview-with-osmesa/8377)._