# There is no paraview executable after build.

**URL:** https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662
**Category:** ParaView Support
**Created:** [September 30, 2018, 2:21am UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662 "2018-09-30T02:21:09Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![govind\_sharma](https://discourse.paraview.org/user_avatar/discourse.paraview.org/govind_sharma/32/370_2.png) [@govind\_sharma](https://discourse.paraview.org/u/govind_sharma)
#### Post date: [September 30, 2018, 2:21am UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/1 "2018-09-30T02:21:09Z")

</div>

Hi All,

Paraview build has been done successfully but as I am not able to run with

./bin/paraview

I have checked bin directory in paraview\_build, there is not paraview executable.  
Only executable with paraview name is paraview-config.

How do I resolve this?

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 30, 2018, 6:33pm UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/2 "2018-09-30T18:33:51Z")

</div>

It’s a little tough to know what might have happened with the information provided. Could you outline a little more your procedure for building ParaView? That may shed some light into what has gone wrong.

---

<div class="post-metadata">

### Author: ![govind\_sharma](https://discourse.paraview.org/user_avatar/discourse.paraview.org/govind_sharma/32/370_2.png) [@govind\_sharma](https://discourse.paraview.org/u/govind_sharma)
#### Post date: [October 1, 2018, 4:43am UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/3 "2018-10-01T04:43:57Z")

</div>

Thanks

1. Source code downloaded via:  
git clone [https://gitlab.kitware.com/paraview/paraview.git](https://gitlab.kitware.com/paraview/paraview.git)  
cd paraview  
git submodule update --init --recursive

2. cd …/  
mkdir paraview\_build  
cd paraview\_build

3. Configure ParaView  
PARAVIEW\_BUILD\_QT\_GUI - OFF  
MPI ON FOR BOTH PARAVIEW AND VTK

4. Configured and generation successfully

5. make -j 4

6. After around 86% make there were errors regarding build testing So I switch BUILD\_TESTING to OFF and  
it worked

7. Again configured and generation, then make -j 4

8. Build successfully

This is the procedure, I followed.

Govind Sharma  
PhD Student  
Indian Institute of Technology, Delhi

---

<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: [October 1, 2018, 7:52am UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/4 "2018-10-01T07:52:52Z")

</div>

`PARAVIEW_BUILD_QT_GUI - OFF` disable the build of the paraview executable. Why are you setting this to OFF ?

---

<div class="post-metadata">

### Author: ![govind\_sharma](https://discourse.paraview.org/user_avatar/discourse.paraview.org/govind_sharma/32/370_2.png) [@govind\_sharma](https://discourse.paraview.org/u/govind_sharma)
#### Post date: [October 1, 2018, 12:24pm UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/5 "2018-10-01T12:24:16Z")

</div>

Thanks,

I have read somewhere that `PARAVIEW_BUILD_QT_GUI` is optional. This option is useful when building ParaView on server nodes or when we are only interested in the Python client, as it avoids building of the Qt client thus does not require Qt. So I did it OFF.

Govind Sharma  
PhD Student  
Indian Institute of Technology, Delhi

---

<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: [October 1, 2018, 12:26pm UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/6 "2018-10-01T12:26:27Z")

</div>

It is optional and correspond to the usecase you are describing. You need it ON in order to build paraview, the GUI.

---

<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: [October 1, 2018, 2:03pm UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/7 "2018-10-01T14:03:30Z")

</div>

On server nodes, the `pvserver`, `pvrenderserver`, and/or `pvdataserver` executables should be used.

---

<div class="post-metadata">

### Author: ![govind\_sharma](https://discourse.paraview.org/user_avatar/discourse.paraview.org/govind_sharma/32/370_2.png) [@govind\_sharma](https://discourse.paraview.org/u/govind_sharma)
#### Post date: [October 3, 2018, 5:47am UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/8 "2018-10-03T05:47:23Z")

</div>

How should I set Qt5\_DIR for paraview configuration. I find there is Qt directory in Paraview folder while it was downloaded. I have also separately downloaded QT5.7.0 source code but don’t know, how do I set it for paraview configuration.

Can anyone tell me the direction to solve this?

Govind Sharma  
PhD Student  
Indian Institute of Technology, Delhi

---

<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: [October 3, 2018, 7:58am UTC](https://discourse.paraview.org/t/there-is-no-paraview-executable-after-build/662/9 "2018-10-03T07:58:55Z")

</div>

Refer to the building paraview documentation.  
[https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md](https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md)  
[https://www.paraview.org/Wiki/ParaView:Build\_And\_Install](https://www.paraview.org/Wiki/ParaView:Build_And_Install)

QT5\_DIR should point to /path/to/qt/install/5.N/gcc\*/lib/cmake/Qt5/
