[vtk-developers] Fixing VTK Python Installation
Brad King
brad.king at kitware.com
Mon Aug 15 18:23:44 EDT 2005
Prabhu Ramachandran wrote:
> We need to decide on the following:
>
> 1. vtk*PythonD, vtk*Python or vtk*Python, vtk*PythonM?
I like the latter but it is working now. There may be problems with
getting the init functions to have the proper name with an M extension.
> 2. Versioning vtkpython, pvtkpython.
Versioning executables like the current shared library versioning works
will require more CMake support. Last week I created a feature request
for it:
http://www.cmake.org/Bug/bug.php?op=show&bugid=2143&pos=0
I think we should just ignore these executables from the python
packaging perspective. I'm not even sure they should be installed at
all. They are meant for running tests. The only reason it makes sense
to install the Tcl executable "vtk" is because it can be built with
static libraries where the system "tclsh" could not load them. Since
the python wrappers require shared libs anyway the system "python"
should always be able to load them from an installation.
-Brad
More information about the vtk-developers
mailing list