# Develop custom paraview-based app with libraries embedded statically

**URL:** https://discourse.paraview.org/t/develop-custom-paraview-based-app-with-libraries-embedded-statically/4882
**Category:** Development
**Created:** [July 18, 2020, 8:46am UTC](https://discourse.paraview.org/t/develop-custom-paraview-based-app-with-libraries-embedded-statically/4882 "2020-07-18T08:46:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Yoshino](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/y/bcef8e/32.png) [@Yoshino](https://discourse.paraview.org/u/Yoshino)
#### Post date: [July 18, 2020, 8:46am UTC](https://discourse.paraview.org/t/develop-custom-paraview-based-app-with-libraries-embedded-statically/4882/1 "2020-07-18T08:46:24Z")

</div>

I have built my app in Release mode, which still depends on paraview dll libraries. And I have to put my exe program into bin directories where all the paraview dependencies are located in order to run.  
I think there should be ways to produce a solo exe program with all the libraries embedded statically(I tried statical plugins and it works). So I built paraview from source again with cmake option **BUILD\_SHARED\_LIBS** set to false, which produced a 3GB lib and seemed cannot be read by application:  
 ![image](https://discourse.paraview.org/uploads/default/original/2X/9/9f1ee13ceac9be014dda3c25d86b4ad98040342a.png)

 ![image](https://discourse.paraview.org/uploads/default/original/2X/3/339051137889ddd0b1589264be2cc0b6dc03d9d2.png)  
thus the build process failed. I’m looking for ways to fix this.

Thanks.

Yoshino

---

<div class="post-metadata">

### Author: ![utkarsh.ayachit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/utkarsh.ayachit/32/39_2.png) [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [July 19, 2020, 12:04pm UTC](https://discourse.paraview.org/t/develop-custom-paraview-based-app-with-libraries-embedded-statically/4882/2 "2020-07-19T12:04:02Z")

</div>

You can work around this issue with by turning off `PARAVIEW_USE_VTKM` cmake option and rebuilding.