[vtk-developers] PythonCore module removal

David Gobbi david.gobbi at gmail.com
Thu Jun 14 11:43:21 EDT 2012


On Thu, Jun 14, 2012 at 9:37 AM, David Lonie <david.lonie at kitware.com> wrote:
> On Thu, Jun 14, 2012 at 10:54 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>> The setup in vtkPython.h isn't legacy, it's still necessary.  But there is
>> no reason for vtkPython.h to include vtkPythonCoreModule.h (which
>> contains the export macros).  If this header is removed from vtkPython.h,
>> then vtkPython.h can go anywhere.
>>
>> It might make sense to merge vtkPython.h and vtkPythonConfigure.h into
>> one file and move them into Common/Core/vtkPython.h.in, i.e. a single,
>> configured header file that is created whenever Python is found.
>>
>> There is also a bunch of python debug library setup that is currently in
>> CMake/vtkWrapPython.cmake that would have to be moved into a
>> separate .cmake file.
>
> This sounds like a good step forward. I'll get back to this project
> early next week and try out some of these ideas, unless you get to it
> first ;-)

Probably the most important thing that has to be done, is that the section of
vtkWrapPython.cmake that starts with if(VTK_WRAP_PYTHON_FIND_LIBS)
should be moved to FindPythonLibs.cmake.  Ideally it should be done
in such a way that that the changes could eventually go into CMake itself
(i.e. variables should be renamed so that they don't contain VTK, etc.)
I'm sure that VTK isn't the only project that needs to find the python debug
libs.

 - David



More information about the vtk-developers mailing list