VTK/Wrappers/Command Line Arguments: Difference between revisions

From KitwarePublic
< VTK‎ | Wrappers
Jump to navigationJump to search
No edit summary
No edit summary
Line 18: Line 18:
|-
|-
| -D <macro[=definition]>
| -D <macro[=definition]>
| add a macro definition
| define a macro (the definition is optional)
|-
|-
| -U <macro>
| -U <macro>

Revision as of 07:08, 10 May 2012

As of VTK 6, the wrapper command-line tools are used as follows:

vtkWrapPython [options] class.h

Many of the options are similar to those of the unix "cc" compiler. The available options are as follows:

option description
-o <file> the output file
-I <dir> add an include directory
-D <macro[=definition]> define a macro (the definition is optional)
-U <macro> undefine a macro
@<file> read command-line arguments from the specified file
--hints <file> hints file, usually called "hints"
--types <file> type hierarchy file, usually ends in "Hierarchy.txt"
--version print the VTK version number of the tool
--help print a short help message
--concrete force the wrappers to wrap the input as a concrete class
--abstract force the wrappers to wrap the input as an abstract class
--vtkobject inform the wrappers that the class is derived from vtkObjectBase
--special inform the wrappers that the class is not derived from vtkObjectBase

The "@file" option allows one or more of the command-line arguments to be stored in a file. If the file that appears after the "@" does not exist, then "@file" will, itself, be treated as a command-line argument. This behavior was chosen for consistency with gcc, which also supports "@" files.