VTK/Wrappers/Command Line Arguments: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Created page with "As of VTK 6, the wrapper command-line tools are used as follows: vtkWrapPython [options] class.h Most of the options are similar to those of the unix "cc" compiler. The availa...") |
No edit summary |
||
| Line 39: | Line 39: | ||
|- | |- | ||
| --concrete | | --concrete | ||
| force the wrappers to | | force the wrappers to wrap the input as a concrete class | ||
|- | |- | ||
| --abstract | | --abstract | ||
| force the wrappers to | | force the wrappers to wrap the input as an abstract class | ||
|- | |- | ||
| --vtkobject | | --vtkobject | ||
Revision as of 06:45, 10 May 2012
As of VTK 6, the wrapper command-line tools are used as follows:
vtkWrapPython [options] class.h
Most 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]> | add a macro definition |
| -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.
