[Paraview-developers] Compile my own plugin with ParaView 4.1.0

[Joe Ping-Lin Hsiao]

I found those libraries were added by linking against ITK libraries. In
ITK, I enabled itkvtkglue, and set the VTK path to ParaView/VTK. Something
must be wrong in the itkvtkglue code, which I am trying to figure out.


On Mon, Apr 21, 2014 at 4:04 PM, Joe Ping-Lin Hsiao <phsiao at cs.unc.edu>wrote:

> I am having trouble to build my plugin with ParaView 4.1.0. I was being
> able to compiling it with 4.1.0-rc.
>
> The problem I have is the plugin is linked with couple .lib that do not
> exist or missing path info. Here is part of my linked libraries:
>
> vtkPythonInterpreter.lib
> vtkWrappingPythonCore.lib
> E:\Joe\lib\build\ParaView-4.1.0\lib\Release\vtkWrappingTools-pv4.1.lib
> E:\Joe\lib\build\ParaView-4.1.0\lib\Release\QtTesting.lib
> E:\Joe\lib\build\ParaView-4.1.0\lib\Release\vtkFiltersTexture-pv4.1.lib
> E:\Joe\lib\build\ParaView-4.1.0\lib\Release\vtkFiltersVerdict-pv4.1.lib
> E:\Joe\lib\build\ParaView-4.1.0\lib\Release\vtkverdict-pv4.1.lib
> vtkRenderingMatplotlib.lib
>
>
> vtkPythonInterpreter.lib, vtkWrappingPythonCore.lib and
> vtkRenderingMatplotlib.lib do not have path info and '-pv4.1' at the end
> like others and when I checked they do not even exist in the ParaView
> binary folder.
>
> When building ParaView, I make sure all the Python related options are
> un-checked. The only change I made was to enable BUILD_SHARED_LIBS. What
> could add those libraries?
>
> Thanks,
> Joe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20140422/052824aa/attachment.html>