Hi,
there was probably a good reason why the Cmake options PARAVIEW_AUTOLOAD_PLUGIN_XXX have been removed, but is there a work around to specify that certain plugins should be automatically loaded? If not, could it be brought back?
Cheers,
Niklas
1 Like
Hi,
is there any other way to automatically load certain plugins? I’d love to configure ParaView on our cluster in a way that users can start right away, and some plugins are mandatory. I would not want every user to first load all the plugins manually. Any help is greatly appreciated.
Thanks and Cheers,
Niklas
Which version of ParaView are you using ?
The latest one, 5.7-RC2
@ben.boeckel : Looks like PARAVIEW_AUTOLOAD_PLUGIN_* cmake option has been removed. Was that intentional ?
@Niklas : You can either
- edit the
lib64/paraview-5.7/plugins/.plugins, - use the env variables PV_PLUGIN_CONFIG_FILE : https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Using_Plugins or
- edit the user space config file.
Yes and no. It was intentional in that the way it got populated before was removed. It was unintentional in that another way to specify it should have been added back.
The best way to add it back is something like:
set(autoload_plugins)
foreach (paraview_plugin IN LISTS paraview_plugins)
option("PARAVIEW_AUTOLOAD_PLUGIN_${paraview_plugin}" "Autoload the ${paraview_plugin} plugin" OFF)
mark_as_advanced("PARAVIEW_AUTOLOAD_PLUGIN_${paraview_plugin}")
if (PARAVIEW_AUTOLOAD_PLUGIN_${paraview_plugin})
list(APPEND autoload_plugins
"${paraview_plugin}")
endif ()
endforeach ()
paraview_plugin_build(… AUTOLOAD ${autoload_plugins})
at the top-level. Docs should be added to the build.md as well.
Thank you both! I’d love to mark both as solution, but can only one…
I got it easily fixed. Thanks for your help!
Cheers, Niklas
I’ve opened an issue here:
https://gitlab.kitware.com/paraview/paraview/issues/19276
1 Like