# Which version of Boost should I use to build ParaView with VisitBridge?

**URL:** https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947
**Category:** ParaView Support
**Created:** [November 10, 2019, 5:07am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947 "2019-11-10T05:07:19Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![lyz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e47774/32.png) [@lyz](https://discourse.paraview.org/u/lyz)
#### Post date: [November 10, 2019, 5:07am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/1 "2019-11-10T05:07:20Z")

</div>

I have build ParaView 5.6 x64 in windows visual studio 2017 successfully. I want to build ParaView with VisitBridge to support more reader. However, I get compile error when I use Boost 1.7 and Boost 1.68 to build solution. Which version of Boost should I use to build ParaView5.6 with VisitBridge?  
Thanks a lot!

---

<div class="post-metadata">

### Author: ![lyz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e47774/32.png) [@lyz](https://discourse.paraview.org/u/lyz)
#### Post date: [November 10, 2019, 6:06am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/2 "2019-11-10T06:06:16Z")

</div>

And I got the error like this. Do I need link some **Boost library**?

 ![Snipaste_2019-11-10_14-05-08](https://discourse.paraview.org/uploads/default/original/2X/6/635afc164848b16d20e3a7390270c2aa493d1336.png)

---

<div class="post-metadata">

### Author: ![lyz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e47774/32.png) [@lyz](https://discourse.paraview.org/u/lyz)
#### Post date: [November 10, 2019, 7:00am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/3 "2019-11-10T07:00:01Z")

</div>

I found the reason. Beacuse I build ParaView using **static** library, so in **class PluginManager** , they use some extern functions as below.  
 ![image](https://discourse.paraview.org/uploads/default/original/2X/1/10630de03d6e5229a0abd0890d3e8bcfce702e11.png)

---

<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: [November 12, 2019, 9:46am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/4 "2019-11-12T09:46:02Z")

</div>

Looks like a bug to me.  
Do you mind opening an issue ?

---

<div class="post-metadata">

### Author: ![lyz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e47774/32.png) [@lyz](https://discourse.paraview.org/u/lyz)
#### Post date: [November 12, 2019, 9:48am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/5 "2019-11-12T09:48:07Z")

</div>

You mean open an issue in github? Sure, thank you.

---

<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: [November 12, 2019, 9:50am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/6 "2019-11-12T09:50:45Z")

</div>

I mean on gitlab :  
[https://gitlab.kitware.com/paraview/paraview/issues](https://gitlab.kitware.com/paraview/paraview/issues)

---

<div class="post-metadata">

### Author: ![lyz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e47774/32.png) [@lyz](https://discourse.paraview.org/u/lyz)
#### Post date: [November 12, 2019, 9:52am UTC](https://discourse.paraview.org/t/which-version-of-boost-should-i-use-to-build-paraview-with-visitbridge/2947/7 "2019-11-12T09:52:13Z")

</div>

OK. I am glad to do this.