# Paraview Master: new build standard use of \`PARAVIEW\_USE\_MPI\`

**URL:** https://discourse.paraview.org/t/paraview-master-new-build-standard-use-of-paraview-use-mpi/1164
**Category:** Development
**Created:** [January 23, 2019, 9:57am UTC](https://discourse.paraview.org/t/paraview-master-new-build-standard-use-of-paraview-use-mpi/1164 "2019-01-23T09:57:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Trophime](https://discourse.paraview.org/user_avatar/discourse.paraview.org/trophime/32/966_2.png) [@Trophime](https://discourse.paraview.org/u/Trophime)
#### Post date: [January 23, 2019, 9:57am UTC](https://discourse.paraview.org/t/paraview-master-new-build-standard-use-of-paraview-use-mpi/1164/1 "2019-01-23T09:57:24Z")

</div>

Hi,  
I don’t quite ketch the comment in latest master commit regarding the new “build” standard:

- ParaView’s flags forcefully disable some modules. For example, ParaView  
can no longer be built with `PARAVIEW_USE_MPI` and still build some  
MPI-releated modules.

Could you please elaborate on this?  
Best

---

<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: [January 23, 2019, 8:15pm UTC](https://discourse.paraview.org/t/paraview-master-new-build-standard-use-of-paraview-use-mpi/1164/2 "2019-01-23T20:15:29Z")

</div>

If `PARAVIEW_USE_MPI` is off, ParaView will not use MPI at all. If it is on, it will turn on important MPI-related modules. Are you seeing errors when building with MPI enabled (I’m working through buildbot errors, so there may be some latent issues). See [https://gitlab.kitware.com/paraview/paraview/merge\_requests/2972](https://gitlab.kitware.com/paraview/paraview/merge_requests/2972) for this work.