# ParaView 5.11 compilation issue on VS2017

**URL:** https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218
**Category:** Development
**Tags:** vtk
**Created:** [January 20, 2023, 12:56pm UTC](https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218 "2023-01-20T12:56:21Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![kvankooten](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kvankooten/32/10280_2.png) [@kvankooten](https://discourse.paraview.org/u/kvankooten)
#### Post date: [January 20, 2023, 12:56pm UTC](https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218/1 "2023-01-20T12:56:21Z")

</div>

Hi,

I’ve been getting a compilation issue on VS2017 using the tagged 5.11.0 PV release from Gitlab, which was fixed a couple of days ago in the paraview/release branch of VTK:

[https://gitlab.kitware.com/vtk/vtk/-/commit/da666ec221e8a2a268b9d85f6a224cbc6762937b](https://gitlab.kitware.com/vtk/vtk/-/commit/da666ec221e8a2a268b9d85f6a224cbc6762937b)

Now I was wondering, if this issue existed for the tagged version of ParaView, which commit was used to produce the official VS2017 PV 5.11 release on the downloads page?

Cheers,  
Kees

---

<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: [January 20, 2023, 1:54pm UTC](https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218/2 "2023-01-20T13:54:22Z")

</div>

I dont know why this issue did not arise (maybe an update change some include logic in visual studio includes) but the commit ParaView commit used for the 5.11 release is the one tagged `v5.11.0`.

Best,

---

<div class="post-metadata">

### Author: ![kvankooten](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kvankooten/32/10280_2.png) [@kvankooten](https://discourse.paraview.org/u/kvankooten)
#### Post date: [January 20, 2023, 1:55pm UTC](https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218/3 "2023-01-20T13:55:37Z")

</div>

Ah right, then I’ll simply adjust the build on my end to account for this, that should be fine. Thanks!

---

<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: [January 20, 2023, 3:13pm UTC](https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218/4 "2023-01-20T15:13:22Z")

</div>

The binaries are built with Visual Studio 2019, which is binary compatible with 2017, hence the labeling (I think). Actually binary compatibility [goes back to 2015](https://learn.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=msvc-170), so if that is the labeling logic, we might consider changing that. @ben.boeckel

---

<div class="post-metadata">

### Author: ![todoooo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/todoooo/32/2819_2.png) [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [January 20, 2023, 11:46pm UTC](https://discourse.paraview.org/t/paraview-5-11-compilation-issue-on-vs2017/11218/5 "2023-01-20T23:46:50Z")

</div>

@mwestphal These issues arise from time to time because the Kitware build servers use VS2019. Microsoft decided to change the header configuration in their C++ source code between VS2017 and VS2019 so sometimes VTK will compile with VS2019 but requires additional includes for VS2017.