# Custom Reader Plugin

**URL:** https://discourse.paraview.org/t/custom-reader-plugin/5685
**Category:** Development
**Created:** [October 29, 2020, 9:18pm UTC](https://discourse.paraview.org/t/custom-reader-plugin/5685 "2020-10-29T21:18:25Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![richti83](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/b9bd4f/32.png) [@richti83](https://discourse.paraview.org/u/richti83)
#### Post date: [October 29, 2020, 9:18pm UTC](https://discourse.paraview.org/t/custom-reader-plugin/5685/1 "2020-10-29T21:18:25Z")

</div>

Hello,  
I developed a reader plugin for lammps/liggghts dump files years ago. I reworked it for the new PV 5.8.1 module structure as shown in the doxygen documentation [1] and it works as expected with the self-compiled ParaView code. When it is loaded into the binary releases for Win (ParaView 5.8.1-Windows-Python3.7-msvc2015-64bit) it complains about undefinied reference to CollectRevisions@vtkObjectBase in reader\_module.dll.  
I used MSVC Version 14.0.25431.01 Update 3, QT5.12.3 and Python 3.8.6 to compile PV from source and pointed CMAKE to the PVB dir when generating the reader plugin.  
Sourcecode and CMake-Files can be found here:

> **[richti83/ParaView\_Reader\_for\_LIGGGHTS](https://github.com/richti83/ParaView_Reader_for_LIGGGHTS/tree/master/reader_src/reader_5.8.1)**
>
> ParaView Reader for LIGGGHTS® DumpFiles. Contribute to richti83/ParaView\_Reader\_for\_LIGGGHTS development by creating an account on GitHub.

  
I guess I’m missing something in the linking stage.  
Thanks for your help,  
Christian.  
[1] [https://kitware.github.io/paraview-docs/v5.8.1/cxx/PluginHowto.html](https://kitware.github.io/paraview-docs/v5.8.1/cxx/PluginHowto.html)

---

<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: [October 30, 2020, 9:23am UTC](https://discourse.paraview.org/t/custom-reader-plugin/5685/2 "2020-10-30T09:23:11Z")

</div>

Build a plugin for the release of ParaView is not trivial, even on Windows. You will need to use the superbuild, the same options and the same compilation chain to ensure compatibility.

---

<div class="post-metadata">

### Author: ![michal.wozniak](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/m/848f3c/32.png) [@michal.wozniak](https://discourse.paraview.org/u/michal.wozniak)
#### Post date: [October 30, 2020, 1:49pm UTC](https://discourse.paraview.org/t/custom-reader-plugin/5685/3 "2020-10-30T13:49:52Z")

</div>

make sure that your local ParaView was build using the following variable VTK\_LEGACY\_REMOVE=ON.

---

<div class="post-metadata">

### Author: ![richti83](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/b9bd4f/32.png) [@richti83](https://discourse.paraview.org/u/richti83)
#### Post date: [October 30, 2020, 5:16pm UTC](https://discourse.paraview.org/t/custom-reader-plugin/5685/4 "2020-10-30T17:16:58Z")

</div>

Thank you Michal,  
this did the trick.
