[Paraview] recommendations to enable additional VTK modules for plugin

[Utkarsh Ayachit]

Pretty much, esp since libproj is a third party module that isn't wrapped.
For other wrapped vtk modules, enabling the module in ParaView will make it
seem like it's just another ParaView module and you wouldn't need to do the
vtk_module_load(..) etc, althogh, wouldn't hurt if you did.




On Wed, Sep 25, 2013 at 9:28 AM, Casey Goodlett
<casey.goodlett at kitware.com>wrote:

> Hi all,
>
> I am working on a plugin and would like to enable an additional VTK module
> that is not normally built by paraview (specifically vtklibproj4).
>
> To enable this I did four things
> 1) Enable Module_vtklibproj4 when building paraview
>
> To my plugin CMakeLists I did the following
>
> 2) Add vtk_module_load(vtklibproj4)
> 3) Add include_directories(${vtklibproj4_INCLUDE_DIRS})
> 4) to target_link_libraries add  ${vtklibproj4_LIBRARIES}
>
> Is this the best way to enable additional VTK modules for plugin
> development?
>
> Thank you
>
> --
> Casey B. Goodlett, Ph.D.
> R&D Engineer
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
>
> _______________________________________________
> 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://www.paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130925/a53434b8/attachment.htm>