[Paraview-developers] BUILD_SHARED_LIBS=OFF and plugins in 4.2.0 rc1

[Utkarsh Ayachit]

1. You cannot dynamically load static plugins. Static plugins need to
be compiled into the ParaView executable. When building ParaView you
can set the PARAVIEW_EXTERNAL_PLUGIN_DIRS cmake variable to point to
external plugin source directories Note, each plugins must include a
plugin.cmake, similar to the Plugins under ParaView source.

2. To load a "compiled in" plugin, use LoadDistributedPlugin() [1]. It
also works with shared builds.

Utkarsh

[1] http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.simple.html#paraview.simple.LoadDistributedPlugin

On Fri, Sep 26, 2014 at 9:20 AM, Favre  Jean <jfavre at cscs.ch> wrote:
>
> I am trying to test a private plugin with static builds.
>
> For ease of use (I thought), I placed my plugin in the same place at the other PV plugins, i.e. in /path-to-source-code/Plugins, and I followed the same syntax as H5PartReader or GMVReader
>
> I have both a shared_libs and a static builds in seperate places. Both of them build and place my plugin in the $CMAKE_INSTALL_PREFIX/lib/paraview-4.2 directories/libprivate.so and
> $CMAKE_INSTALL_PREFIX/lib/paraview-4.2 directories/libprivate.a in the other install place for the static build.
>
> I can load and use my plugin with the shared_libs build. I see it in the GUI and can load it. I can also load it in python via LoadPlugin("...",  ns=globals()) for pvbatch use.
>
> The questions related to the static build.
>
> 1) I cannot see my plugin in the GUI, although it is in the same place as H5PartReader and GMVReader for example.
> 2) I can't figure out how to load any plugins (I also need libEyeDomeLightingView.a ) via LoadPlugin()
>
> Any tip?
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers