Functions | |
| function | vtk_module_python_default_destination (var) |
| Determine Python module destination. More... | |
| function | vtk_module_wrap_python () |
| Wrap a set of modules for use in Python. More... | |
| function | vtk_module_add_python_package (name) |
| Install Python packages with a module. More... | |
| function | vtk_module_add_python_module (name) |
| Use a Python package as a module. More... | |
| function vtk_module_python_default_destination | ( | var | ) |
Determine Python module destination.
Some projects may need to know where Python expects its modules to be placed in the install tree (assuming a shared prefix). This function computes the default and sets the passed variable to the value in the calling scope.
By default, the destination is ${CMAKE_INSTALL_BINDIR}/Lib/site-packages on Windows and ${CMAKE_INSTALL_LIBDIR}/python<VERSION>/site-packages otherwise.
<MAJOR_VERSION> must be one of 2 or 3. If not specified, it defaults to the value of ${VTK_PYTHON_VERSION}.
Definition at line 46 of file vtkModuleWrapPython.cmake.
| function vtk_module_wrap_python | ( | ) |
Wrap a set of modules for use in Python.
MODULES: (Required) The list of modules to wrap.TARGET: (Recommended) The target to create which represents all wrapped Python modules. This is mostly useful when supporting static Python modules in order to add the generated modules to the built-in table.WRAPPED_MODULES: (Recommended) Not all modules are wrappable. This variable will be set to contain the list of modules which were wrapped. These modules will have a INTERFACE_vtk_module_python_package property set on them which is the name that should be given to import statements in Python code.BUILD_STATIC: Defaults to ${BUILD_SHARED_LIBS}. Note that shared modules with a static build is not completely supported. For static Python module builds, a header named <TARGET>.h will be available with a function void <TARGET>_load() which will add all Python modules created by this call to the imported module table. For shared Python module builds, the same function is provided, but it is a no-op.INSTALL_HEADERS (Defaults to ON): If unset, CMake properties will not be installed.TARGET_SPECIFIC_COMPONENTS (Defaults to OFF): If set, prepend the output target name to the install component (<TARGET>-<COMPONENT>).DEPENDS: This is list of other Python modules targets i.e. targets generated from previous calls to vtk_module_wrap_python that this new target depends on. This is used when BUILD_STATIC is true to ensure that the void <TARGET>_load() is correctly called for each of the dependencies.MODULE_DESTINATION: Modules will be placed in this location in the build tree. The install tree should remove $<CONFIGURATION> bits, but it currently does not. See vtk_module_python_default_destination for the default value.STATIC_MODULE_DESTINATION: Defaults to ${CMAKE_INSTALL_LIBDIR}. This default may change in the future since the best location for these files is not yet known. Static libraries containing Python code will be installed to the install tree under this path.CMAKE_DESTINATION: (Required if INSTALL_HEADERS is ON) Where to install Python-related module property CMake files.LIBRARY_DESTINATION (Recommended): If provided, dynamic loader information will be added to modules for loading dependent libraries.PYTHON_PACKAGE: (Recommended) All generated modules will be added to this Python package. The format is in Python syntax (e.g., package.subpackage).SOABI: (Required for wheel support): If given, generate libraries with the SOABI tag in the module filename.INSTALL_EXPORT: If provided, static installs will add the installed libraries to the provided export set.COMPONENT: Defaults to python. All install rules created by this function will use this installation component. Definition at line 582 of file vtkModuleWrapPython.cmake.
Install Python packages with a module.
Some modules may have associated Python code. This function should be used to install them.
The <module> argument must match the associated VTK module that the package is with. Each package is independent and should be installed separately. That is, package and package.subpackage should each get their own call to this function.
PACKAGE: (Required) The package installed by this call. Currently, subpackages must have their own call to this function.FILES: (Required) File paths should be relative to the source directory of the calling CMakeLists.txt. Upward paths are not supported (nor are checked for). Absolute paths are assumed to be in the build tree and their relative path is computed relative to the current binary directory.MODULE_DESTINATION: Modules will be placed in this location in the build tree. The install tree should remove $<CONFIGURATION> bits, but it currently does not. See vtk_module_python_default_destination for the default value.COMPONENT: Defaults to python. All install rules created by this function will use this installation component.A <module>-<package> target is created which ensures that all Python modules have been copied to the correct location in the build tree.
Definition at line 1000 of file vtkModuleWrapPython.cmake.
Use a Python package as a module.
If a module is a Python package, this function should be used instead of vtk_module_add_module.
PACKAGES: (Required) The list of packages installed by this module. These must have been created by the vtk_module_add_python_package function. Definition at line 1098 of file vtkModuleWrapPython.cmake.
1.8.13 on Wed Jan 27 2021