Hi Hong,
There won't be a separate library created for Python wrapping your plugin
for doing ParaView. Did you add in the following to your adaptor:
#ifndef BUILD_SHARED_LIBS
#include pvStaticPluginsInit.h
#endif
And then in the adaptor initialization step you should have something in it
like:
Hi Andy,
That is exactly what I did, and I also modified CMakeLists.txt to link
${PARAVIEW_PLUGINLIST} to the target via target_link_libraries. However, the
symbol pv_plugin_instance_SMVorticity is undefined in the built target static
library, while following the same process to build pvbatch
Hmm, I would check the link line for your adaptor and for creating the
executable to see if the plugin library is included there. Something else
you can try is explicitly create the plugin's filter in the adaptor code to
make sure that it is linked in properly.
Regards,
Andy
On Thu, Oct 3, 2013
Thanks for the helpful info, Andy. I looked at the link and followed the code
change Burlen posted to add the static linked plugin initialization into
pvbatch and pvpython and that worked fine. Now pvbatch and pypthon all have my
filter plugin statically loaded. I still got the name not defined
Hi Hong,
I don't think you want to do VTK Python wrapping of your class. What you
want is to have the proxy to the filter Python wrapped such that it's
available when you import paraview.simple. This is what's needed for
Catalyst Python pipelines. I don't think you're properly initializing the
Thanks, Andy. The CMakeLists.txt for my plugin is copied below with newly added
lines for python wrapping in orange:
-
if(NOT ParaView_SOURCE_DIR)
find_package(ParaView)
include(${PARAVIEW_USE_FILE})
include (ParaViewPlugins)
else()
# we're building from
Can you share your plugin or at least the CMakeLists.txt for your plugin?
Have you tried with any other plugins that get packaged with ParaView to
see if they work?
If you're using Catalyst, I would suggest adding in the
PV_PLUGIN_IMPORT_INIT macros to the adaptor.
Andy
On Thu, Sep 26, 2013 at
I think that information is out of date. I believe that is done
automatically now.
Otherwise Andy is right. Putting the filter inside a plugin a good way to
go. The plugin infrastructure will make it so that when you provide the XML
that describes your vtk class, ParaView's build system will
Utkarsh pointed out that you still need to follow
http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications
when the plugin is external to ParaView. If you put your plugin inside
ParaView/Plugins, then it is done automatically.
David E DeMarle
Kitware, Inc.
RD Engineer
21
Thanks! I did put my plugin inside ParaView/Plugins in the same way as other
Plugins, and enabled it when building ParaView superbuild on Titan. I can see
the static lib for the Plugin is built in paraview-build/lib directory. And
yes, I did use a plugin and load it via Tools|Manage Plugins
Hello,
I set up a pipeline that used a custom filter I developed and exported it as a
python script for coprocessing. I have made sure the static library for my
custom filter is built and available in paraview-build/lib directory, and I
have also linked this custom filter static library along
Did you use a plugin to add in your custom filter when creating the Python
co-processing script? I'm not sure how plugins are loaded for static
builds but you may want to look at
http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications.
If that doesn't work, we'll have to
12 matches
Mail list logo
