# Building Paraview "from scratch" in order to use a custom plugin

**URL:** https://discourse.paraview.org/t/building-paraview-from-scratch-in-order-to-use-a-custom-plugin/4233
**Category:** ParaView Support
**Created:** [May 1, 2020, 7:50am UTC](https://discourse.paraview.org/t/building-paraview-from-scratch-in-order-to-use-a-custom-plugin/4233 "2020-05-01T07:50:12Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![dutta-alankar](https://discourse.paraview.org/user_avatar/discourse.paraview.org/dutta-alankar/32/13310_2.png) [@dutta-alankar](https://discourse.paraview.org/u/dutta-alankar)
#### Post date: [May 1, 2020, 2:47pm UTC](https://discourse.paraview.org/t/building-paraview-from-scratch-in-order-to-use-a-custom-plugin/4233/4 "2020-05-01T14:47:44Z")

</div>

Hi Naveen,

I pull only Superbuild from Git. That’s all I need. Everything else is downloaded separately on its own depending on the cmake file I have provided (including Paraview) during the build process. To install a specific version of Paraview make sure you checkout for that particular version in superbuild git repo.

@npillai2 Please let me know if you face any problem.  
PS: Builds with Ninja is less buggy and you may try that instead of what I did in `config.sh`. I also build everything in a folder outside the superbuild directory.

---

_[View the full topic](https://discourse.paraview.org/t/building-paraview-from-scratch-in-order-to-use-a-custom-plugin/4233)._