The problem stems because ParaView doesn't enable the vtkImagingStencil by default. In your ParaView build, turn on Module_vtkImagingStencil CMake flag and then rebuild ParaView and your plugin.
On Thu, Dec 11, 2014 at 3:48 AM, Dr. Roman Grothausmann <[email protected]> wrote: > Dear Utkarsh, > > > Finally, after visiting the paraview workshop in Lyon, I got my own paraview > plugin based on c++ for this old task to compile and link. However, already > when loading it as a module in paraview, paraview crashes with a symbol > lookup error: > > /opt/paraview-4.1.0_debug/bin/paraview > /opt/paraview-4.1.0_debug/lib/paraview-4.1/paraview: symbol lookup error: > /net/home/grothama/vtk/paraview_plugins/image-clipper/build/libmyImageClipper.so: > undefined symbol: _Z19myImageClipper_InitP26vtkClientServerInterpreter > > What could be the problem for this? How can I debug this problem? > I tried to combine things from > ParaViewCore/VTKExtensions/Default/vtkPVMetaSliceDataSet.cxx and from Your > XML to use a vtkImplicitFunction as an input to a filter. I had to copy > > cp ParaView-v4.1.0/VTK/Imaging/Stencil/*.h > ParaView-v4.1.0/build_141124/VTK/Imaging/Stencil/ > > and to add > CMAKE_CXX_FLAGS -I ParaView-v4.1.0/build_141124/VTK/Imaging/Stencil/ > > for vtkImplicitFunctionToImageStencil.h to be found by cmake. However, the > error does not seem to be caused by the stencil stuff. Attached are the > files. > > Thanks for any help or hints > Roman > > > > On 26/08/13 15:06, Utkarsh Ayachit wrote: >>> >>> Many thanks for Your reply, Your effort to create an XML-plugin and the >>> bug >>> report. Would it help to compile paraview from source with >>> Module_vtkImagingStencil set to ON on our own platform for testing or is >>> there some code adjustment of paraview necessary to allow that? >> >> >> No, it won't help. I did exactly that an ran into issues with >> vtkImageStencil and ParaView. Evidently, we hadn't tried to use that >> data-object in ParaView before. >> >>> I guess it would not help to specify the location of a separately >>> compiled vtk-5.10? >> >> >> You are correct, it will not help. We need to track the issue down on >> the ParaView side first. >> >>> Do I understand correctly that with using port_index= You specify which >>> output should go to which input? >> >> >> That is correct. If not specified, 0 is assumed. >> >>> What is calling e.g. the vtkImplicitPlaneWidget to get the interaction >>> widget for specifying the implicit function parameters? >> >> >> In this case, it's the "ProxyListDomain" associated with the >> "ImplicitFunction" property. The domain refers to proxies viz. >> ("implicit_functions", "Plane"), etc. If you look at the xml >> definitions for the same in ParaView >> (ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml), >> you'll see that it provides a "<Hints>" section that suggests a >> "PropertyGroup" of type "Plane". That's what's causing the GUI to show >> the vtkImplicitPlaneWidget to control the Origin and Normal >> properties. >> >> Hope that clarifies things a bit. >> >> Utkarsh >> > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Institut für Funktionelle und Angewandte Anatomie, OE 4120 > Medizinische Hochschule Hannover > Carl-Neuberg-Str. 1 > D-30625 Hannover > > Tel. +49 511 532-9574 _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
