# proper paraview development build on debian/ubuntu

**URL:** https://discourse.paraview.org/t/proper-paraview-development-build-on-debian-ubuntu/4334
**Category:** ParaView Support
**Created:** [May 14, 2020, 9:59pm UTC](https://discourse.paraview.org/t/proper-paraview-development-build-on-debian-ubuntu/4334 "2020-05-14T21:59:05Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![olesenm](https://discourse.paraview.org/user_avatar/discourse.paraview.org/olesenm/32/17416_2.png) [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [May 14, 2020, 9:59pm UTC](https://discourse.paraview.org/t/proper-paraview-development-build-on-debian-ubuntu/4334/1 "2020-05-14T21:59:05Z")

</div>

I installed paraview 5.7.0 (and paraview-dev) on Ubuntu 20.04 using `apt` packages, not the pre-built binaries. The main reasons are trying to do things within the debian/ubuntu build system, but also to build custom plugins using these _system_ installed packages.

At first glance it looked OK, but noticed that they forgot to include some cmake files (noted in this [debian bug report](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959387)). This looked easy enough, so I forked their build and added a few more files to be installed (the various vtkWrapXX binaries were also missing).  
After reinstalling these newly compiled packages, I tried using them for the plugins. The usual minor bits about not having all of the make dependencies (eg, libavdevice-dev …), but nothing alarming.

However, I struck a large roadblock with the MPI detection failing and from there things just got worse.  
Has anyone (kitware, elsewhere @mwestphal??) got this working?

My scratch pad of changes is on a [WIP merge request for review](https://salsa.debian.org/science-team/paraview/-/merge_requests/1/diffs)

If there is more/less that should be there, I would be grateful for input. It would be nice to get this properly sorted.

Cheers,  
/mark

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 14, 2020, 11:13pm UTC](https://discourse.paraview.org/t/proper-paraview-development-build-on-debian-ubuntu/4334/2 "2020-05-14T23:13:21Z")

</div>

I don’t know how Debian does it, but Fedora uses a separate prefix for MPI libraries (e.g., `/usr/lib64/mpich` or `/usr/lib64/openmpi` on Fedora). This is because they tend to have SONAME conflicts. You may need to add this prefix to `CMAKE_PREFIX_PATH` for the correct MPI to be found.