[Paraview] Example project: vtk libraries, python wrappers, paraview plugin

[Utkarsh Ayachit]

Yup, something's definitely broken. The pv_setup_module_environment()
was written while VTK modules logic we still being revised so things
may have changed. I'll give it a look.

Utkarsh

On Mon, Jul 8, 2013 at 1:36 PM, Pat Marion <pat.marion at kitware.com> wrote:
> Hi,
>
> After AutobahnPython and related ones, it complains about smTestDriver,
> vtkEyeDomeLighting, vtkPVCatalyst, and many more.  Is it possible that the
> cmake code that computes the list VTK_MODULES_ENABLED isn't correct?  Here's
> the contents of VTK_MODULES_ENABLED:
>
> AutobahnPython
> Twisted
> ZopeInterface
> pqApplicationComponents
> pqComponents
> pqCore
> pqPython
> pqWidgets
> smTestDriver
> vtkChartsCore
> vtkClientServer
> vtkCommonColor
> vtkCommonComputationalGeometry
> vtkCommonCore
> vtkCommonDataModel
> vtkCommonExecutionModel
> vtkCommonMath
> vtkCommonMisc
> vtkCommonSystem
> vtkCommonTransforms
> vtkCosmo
> vtkDICOMParser
> vtkDomainsChemistry
> vtkEyeDomeLighting
> vtkFiltersAMR
> vtkFiltersCore
> vtkFiltersCosmo
> vtkFiltersExtraction
> vtkFiltersFlowPaths
> vtkFiltersGeneral
> vtkFiltersGeneric
> vtkFiltersGeometry
> vtkFiltersHybrid
> vtkFiltersHyperTree
> vtkFiltersModeling
> vtkFiltersParallel
> vtkFiltersParallelStatistics
> vtkFiltersProgrammable
> vtkFiltersSources
> vtkFiltersStatistics
> vtkFiltersTexture
> vtkFiltersVerdict
> vtkGUISupportQt
> vtkIOAMR
> vtkIOCore
> vtkIOEnSight
> vtkIOExodus
> vtkIOExport
> vtkIOGeometry
> vtkIOImage
> vtkIOImport
> vtkIOInfovis
> vtkIOLSDyna
> vtkIOLegacy
> vtkIOMovie
> vtkIONetCDF
> vtkIOPLY
> vtkIOParallel
> vtkIOParallelExodus
> vtkIOParallelLSDyna
> vtkIOVPIC
> vtkIOXML
> vtkIOXMLParser
> vtkIOXdmf2
> vtkImagingColor
> vtkImagingCore
> vtkImagingFourier
> vtkImagingGeneral
> vtkImagingHybrid
> vtkImagingMorphological
> vtkImagingSources
> vtkInfovisCore
> vtkInteractionImage
> vtkInteractionStyle
> vtkInteractionWidgets
> vtkMetaIO
> vtkPVCatalyst
> vtkPVClientServerCoreCore
> vtkPVClientServerCoreDefault
> vtkPVClientServerCoreRendering
> vtkPVCommon
> vtkPVPythonCatalyst
> vtkPVServerImplementationCore
> vtkPVServerImplementationDefault
> vtkPVServerImplementationRendering
> vtkPVServerManagerApplication
> vtkPVServerManagerCore
> vtkPVServerManagerDefault
> vtkPVServerManagerRendering
> vtkPVVTKExtensionsCore
> vtkPVVTKExtensionsDefault
> vtkPVVTKExtensionsRendering
> vtkPVVTKExtensionsWebGLExporter
> vtkParaViewWeb
> vtkParaViewWebApplications
> vtkParaViewWebCore
> vtkParaViewWebJavaScript
> vtkParaViewWebPython
> vtkParaViewWebWidgets
> vtkParallelCore
> vtkParseOGLExt
> vtkPointSpriteGraphics
> vtkPointSpriteRendering
> vtkPython
> vtkPythonInterpreter
> vtkQvis
> vtkRenderingAnnotation
> vtkRenderingContext2D
> vtkRenderingCore
> vtkRenderingFreeType
> vtkRenderingFreeTypeOpenGL
> vtkRenderingGL2PS
> vtkRenderingHybridOpenGL
> vtkRenderingLOD
> vtkRenderingLabel
> vtkRenderingMatplotlib
> vtkRenderingOpenGL
> vtkRenderingParallel
> vtkRenderingVolume
> vtkRenderingVolumeAMR
> vtkRenderingVolumeOpenGL
> vtkTestingCore
> vtkTestingRendering
> vtkUtilitiesEncodeString
> vtkUtilitiesHashSource
> vtkUtilitiesMaterialLibrary
> vtkUtilitiesProcessXML
> vtkUtilitiesPythonInitializer
> vtkUtilitiesWrapClientServer
> vtkVPIC
> vtkViewsContext2D
> vtkViewsCore
> vtkWrappingPythonCore
> vtkWrappingTools
> vtkalglib
> vtkexodusII
> vtkexpat
> vtkfreetype
> vtkftgl
> vtkgl2ps
> vtkhdf5
> vtkjpeg
> vtkjsoncpp
> vtklibxml2
> vtknetcdf
> vtkoggtheora
> vtkpng
> vtkprotobuf
> vtkqttesting
> vtksys
> vtktiff
> vtkverdict
> vtkxdmf2
> vtkzlib
>
>
>
> On Mon, Jul 8, 2013 at 10:56 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>>
>> I am thinking the problem is stemming from the non-traditional module
>> "AutobahnPython". It doesn't generate the module cmake file. That
>> needs to be fixed. In the mean time, you can try retry the same by
>> turning off PARAVIEW_ENABLE_WEB cmake flag, and verify.
>>
>> Utkarsh
>>
>>
>>
>> On Fri, Jul 5, 2013 at 12:34 PM, Pat Marion <pat.marion at kitware.com>
>> wrote:
>> > Hi,
>> >
>> > I wanted to setup a project that built VTK libraries using the modern
>> > vtk
>> > module cmake code, added Python wrapping to the VTK libraries, and then
>> > built a ParaView plugin that linked against the VTK libraries.
>> >
>> > Traditionally, a ParaView plugin is created by compiling all the cxx
>> > files
>> > into the plugin library, but I wanted my files compiled into a standard
>> > VTK
>> > module library, and I wanted Python wrappers so that I could import my
>> > vtk
>> > module library in Python.
>> >
>> > Here's the example project.
>> >
>> > https://github.com/patmarion/PythonWrappedPluginExample
>> >
>> >
>> > It works, I tested it on ParaView master, but I had to comment out some
>> > lines in ParaViewPlugins.cmake to avoid configure errors.  If a someone
>> > who
>> > knows the pv_setup_module_environment() macro wants to give this a shot
>> > and
>> > see why it doesn't work, please let me know!  It seems that
>> > pv_setup_module_environment() is broken:
>> >
>> > CMake Error at ParaView/VTK/CMake/vtkModuleAPI.cmake:44 (message):
>> >   No such module: "AutobahnPython"
>> > Call Stack (most recent call first):
>> >   ParaView/CMake/ParaViewPlugins.cmake:1300 (vtk_module_load)
>> >   Module/CMakeLists.txt:2 (pv_setup_module_environment)
>> >
>> >
>> > I had to comment out a foreach loop to make it configure:
>> >
>> > diff --git a/CMake/ParaViewPlugins.cmake b/CMake/ParaViewPlugins.cmake
>> > index dcf53f9..12b139e 100644
>> > --- a/CMake/ParaViewPlugins.cmake
>> > +++ b/CMake/ParaViewPlugins.cmake
>> > @@ -1296,7 +1296,8 @@ macro(pv_setup_module_environment _name)
>> >    include(vtkModuleAPI)
>> >    include(vtkClientServerWrapping)
>> >    # load information about existing modules.
>> > -  foreach (mod IN LISTS VTK_MODULES_ENABLED)
>> > -    vtk_module_load("${mod}")
>> > -  endforeach()
>> > +  #foreach (mod IN LISTS VTK_MODULES_ENABLED)
>> > +  #  vtk_module_load("${mod}")
>> > +  #  endif()
>> > +  #endforeach()
>> >  endmacro()
>> >
>> >
>> > Pat
>> >
>> > _______________________________________________
>> > 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
>> >
>
>