Hello, we have a legacy implementation of a PV reader plugin which is patched into the PV code.
I want to refactor this approach to an external plugin. In https://gitlab.kitware.com/paraview/paraview-superbuild it says: ————- External plugins The superbuild supports building more plugins into ParaView using the paraviewexternalplugins project. As an example, to build two external plugins a and b, the following settings should be used: • enable_paraviewexternalplugins:BOOL=ON: Enables building using external plugins. • paraview_PLUGINS_EXTERNAL:STRING=a;b: The list of plugins to build. • paraview_PLUGIN_a_PATH:PATH=/path/to/plugin/a: The path to plugin a's source directory. It must contain a plugins.cmake to be picked up by ParaView. —————— Sounds good, I assumed I have to add this via -D to the superbuild cmake, however it tells me CMake Warning: Manually-specified variables were not used by the project: enable_paraviewexternalplugins And indeed I could not find anything about this, not in the code and not with google. what do I miss? I there somewhere an example or documentation? Is this something new with 5.2? Thanks for any help, Fabian _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
