# 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:** 31

<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 12, 2020, 6:44am UTC](https://discourse.paraview.org/t/building-paraview-from-scratch-in-order-to-use-a-custom-plugin/4233/31 "2020-05-12T06:44:28Z")

</div>

@npillai2  
I remember getting an error similar to this back in January while trying to compile Paraview. But I can’t recall what exactly solved the issue.  
Have you tried these?

> set(ENABLE\_osmesa OFF CACHE BOOL “”)  
> set(mesa\_SWR\_ARCH “avx,avx2” CACHE STRING “”)

I’m not sure why but I remember for OsMesa I was advised to try this.  
You can see the thread of this [post](https://discourse.paraview.org/t/llvm-compilation-error-during-paraview-compiling-on-cray-xc40/3299/6) for reference

---

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