Catalyst Build: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 2: Line 2:
The Catalyst source tree is generated from ParaView using a Python script located in the ParaView source tree ([http://http://paraview.org/gitweb?p=ParaView.git;a=blob;f=Catayst/catalyze.py] Catalyst/catalyze.py). The script takes a JSON manifest file (manifest.json) that describes what files are copied and transform from ParaView to produce the Catalyst source tree. For example the following segment of JSON indicates that the VTK module vtkCommonMath should be included (excluding the Testing directory) and it should be Python wrapped:
The Catalyst source tree is generated from ParaView using a Python script located in the ParaView source tree ([http://http://paraview.org/gitweb?p=ParaView.git;a=blob;f=Catayst/catalyze.py] Catalyst/catalyze.py). The script takes a JSON manifest file (manifest.json) that describes what files are copied and transform from ParaView to produce the Catalyst source tree. For example the following segment of JSON indicates that the VTK module vtkCommonMath should be included (excluding the Testing directory) and it should be Python wrapped:


<source lang="json">
<source lang="javascript">


     {
     {

Revision as of 18:48, 7 November 2012

Generating Catalyst Source Tree

The Catalyst source tree is generated from ParaView using a Python script located in the ParaView source tree ([1] Catalyst/catalyze.py). The script takes a JSON manifest file (manifest.json) that describes what files are copied and transform from ParaView to produce the Catalyst source tree. For example the following segment of JSON indicates that the VTK module vtkCommonMath should be included (excluding the Testing directory) and it should be Python wrapped:

<source lang="javascript">

   {
     "name":"vtkCommonMath",
     "path":"VTK/Common/Math",
     "exclude":[
       {
         "path":"Testing"
       }
     ],
     "pythonwrap":true
   }

</source>

Build Directions