# Custom plugin - Requirements for plugin compatible with release \[Windows\]

**URL:** https://discourse.paraview.org/t/custom-plugin-requirements-for-plugin-compatible-with-release-windows/10972
**Category:** Development
**Created:** [December 14, 2022, 2:19pm UTC](https://discourse.paraview.org/t/custom-plugin-requirements-for-plugin-compatible-with-release-windows/10972 "2022-12-14T14:19:02Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![MCO](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mco/32/10402_2.png) [@MCO](https://discourse.paraview.org/u/MCO)
#### Post date: [December 14, 2022, 2:19pm UTC](https://discourse.paraview.org/t/custom-plugin-requirements-for-plugin-compatible-with-release-windows/10972/1 "2022-12-14T14:19:02Z")

</div>

Hi everyone,

We plan to developp a plugin, that users may use with the latest release.

On Windows, [the latest release of paraview (5.11.0)](https://www.paraview.org/download/) is build with msvc2017, whereas the [documentation](https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md) suggests to setup the dev environnment with msvc2019.

Thus we would like to know :

- The versions use to build the latest release

- Where to find this information for each release (past and future)

- Finaly for each requirement, must the plugin be built wtih the same (==) or a higher version (\>=) to work with the release ?

---

<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: [December 14, 2022, 2:42pm UTC](https://discourse.paraview.org/t/custom-plugin-requirements-for-plugin-compatible-with-release-windows/10972/2 "2022-12-14T14:42:32Z")

</div>

Hi @MCO

The process to build a plugin compatible with with Windows Binary Release is here:  
[https://gitlab.kitware.com/paraview/paraview-plugin-windows-binary-compatible-guide](https://gitlab.kitware.com/paraview/paraview-plugin-windows-binary-compatible-guide)

Visual Studio Version should not have an impact.

Best,

---

<div class="post-metadata">

### Author: ![MCO](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mco/32/10402_2.png) [@MCO](https://discourse.paraview.org/u/MCO)
#### Post date: [December 14, 2022, 3:49pm UTC](https://discourse.paraview.org/t/custom-plugin-requirements-for-plugin-compatible-with-release-windows/10972/3 "2022-12-14T15:49:24Z")

</div>

Thank you Mathieu for this quick answer.

I still have two questions.

# First Point

Your answer suggests that a plugin build with msvc 2019 is compatible with the latest release, but what about QT ?

I asked this question as my plugin works with the local build paraview (msvc2019-QT5.15.12) but not with the latest downloaded version (5.11 msvc2017-QT ???).

In this latest release, the plugin is loaded but crashes once QT interactions start.

# Second Point

I will try the process shared (with superbuild), it may not help but simplify the process. Nevertheless I do not find the 5.11 configurations file in [the shared “Guide Repo”.](https://gitlab.kitware.com/paraview/paraview-plugin-windows-binary-compatible-guide). Is it the same as 5.10.1 ?

---

<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: [December 14, 2022, 3:57pm UTC](https://discourse.paraview.org/t/custom-plugin-requirements-for-plugin-compatible-with-release-windows/10972/4 "2022-12-14T15:57:10Z")

</div>

> I asked this question as my plugin works with the local build paraview (msvc2019-QT5.15.12) but not with the latest downloaded version (5.11 msvc2017-QT ???).

I’ll check and let you know.

> not find the 5.11 configurations file in [the shared “Guide Repo”.](https://gitlab.kitware.com/paraview/paraview-plugin-windows-binary-compatible-guide). Is it the same as 5.10.1 ?

Not updated yet, should be close enough anyway.
