# SuperBuild and plugin.

**URL:** https://discourse.paraview.org/t/superbuild-and-plugin/2209
**Category:** ParaView Support
**Created:** [July 12, 2019, 3:50pm UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209 "2019-07-12T15:50:41Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![paskino](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/258eb7/32.png) [@paskino](https://discourse.paraview.org/u/paskino)
#### Post date: [July 12, 2019, 3:50pm UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/1 "2019-07-12T15:50:41Z")

</div>

Hallo

I’m trying to build ParaView with the superbuild. It does actually work, but I’m not getting the Qt GUI. Reading [here](https://gitlab.kitware.com/paraview/paraview-superbuild#projects-and-features) I was lead to think that `ENABLE_qt5` would suffice.

But after the build I “only” got `pvbatch pvdataserver pvpython pvrenderserver pvserver`.

What am I missing?

Secondly, I’m building my own plugin. The wiki refers always to `find(ParaView)` but my CMake complains that no `FindParaView.cmake` is to be found.

I did manage to build the plugin by pointing to the `ParaViewConfig.cmake` file, but I’m wondering whether the docs are just outdated or I don’t see something obvious.

Thanks

Edo

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 15, 2019, 8:52am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/2 "2019-07-15T08:52:15Z")

</div>

Which version of ParaView are you using ?

Regarding your superbuild question, you need ENABLED\_qt5 and ENABLE\_paraview.

Why are you building the superbuild anyway ? If you want to only use ParaView locally, I would recommend to go with ParaView alone.

Regarding the CMake questions, you always need to point to a build dir of ParaView, and unless specific configuration, cmake can’t find it.

Which docs are your referring ?

---

<div class="post-metadata">

### Author: ![paskino](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/258eb7/32.png) [@paskino](https://discourse.paraview.org/u/paskino)
#### Post date: [July 15, 2019, 9:09am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/3 "2019-07-15T09:09:29Z")

</div>

Hi Mathieu,

I’m using ParaView 5.6.1.

I am building a custom plugin. When I first started I built ParaView and then passed the directory of the build to CMake and built my project. But this involved a lot of manual steps and I wanted to avoid those. For this reason I created a CMake Project which would build the plugin and ParaView together.

In the [wiki](https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Writing_Plugins) you find these lines

```auto
FIND_PACKAGE(ParaView REQUIRED)
INCLUDE(${PARAVIEW_USE_FILE})

```

So far I’ve not been able to find `FindParaView.cmake` anywhere.

Thanks

Edo

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 15, 2019, 9:12am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/4 "2019-07-15T09:12:59Z")

</div>

You have to set ParaView\_DIR to your build dir of ParaView when configuring your plugin.

---

<div class="post-metadata">

### Author: ![paskino](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/258eb7/32.png) [@paskino](https://discourse.paraview.org/u/paskino)
#### Post date: [July 15, 2019, 9:22am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/5 "2019-07-15T09:22:11Z")

</div>

That’s what I do. But the call `FIND_PACKAGE(ParaView)` does not work as the `FindParaView.cmake` doesn’t exist anywhere (I know).

One has to include the `ParaViewConfig.cmake` file rather than calling `find_package`.

Edo

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 15, 2019, 9:25am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/6 "2019-07-15T09:25:55Z")

</div>

The absence of FindParaView.cmake does not prevent cmake for finding ParaView. You can provide one if you want, but it is not a necessity.

If you set the ParaView\_DIR to the build directory of ParaView, then you are doing it exactly the right way.

---

<div class="post-metadata">

### Author: ![paskino](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/258eb7/32.png) [@paskino](https://discourse.paraview.org/u/paskino)
#### Post date: [July 15, 2019, 9:30am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/7 "2019-07-15T09:30:36Z")

</div>

Hi,

my point is, is the command `FIND_PACKAGE(ParaView)` existing (or better `FindParaView.cmake`)? If not, it should not be written in the [documentation](https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Writing_Plugins).

In this case the docs should state to include the file `ParaViewConfig.cmake` that is somewhere in the build tree.

Edo

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 15, 2019, 9:35am UTC](https://discourse.paraview.org/t/superbuild-and-plugin/2209/8 "2019-07-15T09:35:46Z")

</div>

> CMake will ask for the ParaView\_DIR which you point to your ParaView build.

What’s unclear about that in the documentation ?

Find\*.cmake are usually provided by other means, either CMake or your own distribution, not by the software itself.