[vtk-developers] Should vtkTclUtils, vtkPythonUtils, vtkJavaUtils be moved to "Wrapping"?

[David Gobbi]

On Tue, May 4, 2010 at 8:26 AM, Mathieu Malaterre
<mathieu.malaterre at gmail.com> wrote:
> Yes !
>
> debian packaging ships those files in wrapping related package and not
> the main dev one (eg. vtkJavaUtil.h is in package libvtk-java).
>
> Mathieu

I've been looking for a good way to do this, but it isn't easy.  Right
now vtkPythonUtil.cxx file is built into libvtkCommonPythonD.so and
has its exports set up for this library.  So if I move
vtkPythonUtil.cxx to VTK/Wrapping/Python, then I have to make a whole
new shared library and have libvtkCommonPythonD.so link to this new
library.  Is it worth it, I wonder?

The link situation would be like this, where "libvtkPython.so" is the
new library:

libvtkCommonPython.so -> libvtkCommonPythonD.so -> libvtkPython.so ->
libvtkCommon.so

The same for Java and Tcl.  Actually I think this is not so bad.

   David