[Paraview] Plugin Crashing on PV 3.12 RC2

David E DeMarle dave.demarle at kitware.com
Tue Jul 15 16:45:08 EDT 2014


The syntax has changed repeatedly over the years.

I _think_ that the magic you are missing is currently buried underneath the
CMake call to pv_process_modules.

That configures a file that makes void @PLUGIN_NAME at _CombinedInitialize()
that paraview calls at run time to make those CS wrapped classes
instantiable by the process module. (or something like that)

Seb and Utkarsh know this part of the code very well. You should bug them
off list and then post on list with an simplified answer that normal humans
can follow.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Tue, Jul 15, 2014 at 4:24 PM, Matthew Woehlke <
matthew.woehlke at kitware.com> wrote:

> On 2014-07-15 16:08, David E DeMarle wrote:
> > The trick is that you have to make sure that the VTK classes are wrapped
> > into paraview's client server language and instantiable at run time.
> Check
> > the Manta View plugin for an example.
>
> Yes, I figured that... I still don't see how to actually do that,
> though. (I don't see where paraview/Plugins/MantaView - is that what you
> meant? - is doing that... or indeed, doing anything substantively
> different that what I'm doing.)
>
> I tried adding this:
>
>   include(vtkClientServerWrapping)
>   vtk_add_cs_wrapping(MyLib)
>   target_link_libraries(MyPlugin MyLibCS)
>
> ...but to no effect :-(. (It generates the CS library, but I still get
> the same error.)
>
> --
> Matthew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140715/e771aa84/attachment-0001.html>


More information about the ParaView mailing list