tags 572139 moreinfo
thanks
GDCM is building VTK/Python extension without any issue since VTK 5.0.
It is using cmake to handle all the nasty work, and seems to have been
quite a decent job on debian either. I think we need to see the OP
cmake code to decide whether we should close this bug or not.
Here is the code in GDCM that handle VTK 4.0 to VTK 5.8 style to
building vtk/python extension:
IF(GDCM_WRAP_PYTHON)
IF(VTK_WRAP_PYTHON)
SET(DEXTENSION "")
IF( "${VTK_MAJOR_VERSION}.${VTK_MINOR_VERSION}" LESS 4.5 )
VTK_WRAP_PYTHON2(${VTKGDCM_NAME}Python vtkgdcmPYTHON_SRCS
${vtkgdcm_SRCS})
ELSE( "${VTK_MAJOR_VERSION}.${VTK_MINOR_VERSION}" LESS 4.5 )
INCLUDE(${VTK_CMAKE_DIR}/vtkWrapPython.cmake)
INCLUDE_DIRECTORIES(
${PYTHON_INCLUDE_DIR}
${CMAKE_CURRENT_SOURCE_DIR}
)
VTK_WRAP_PYTHON3(${VTKGDCM_NAME}Python vtkgdcmPYTHON_SRCS
"${vtkgdcm_SRCS}")
SET(DEXTENSION "D")
ENDIF( "${VTK_MAJOR_VERSION}.${VTK_MINOR_VERSION}" LESS 4.5 )
ADD_LIBRARY(${VTKGDCM_NAME}PythonD ${vtkgdcmPYTHON_SRCS})
# this is a library set the version:
ADD_LIBRARY(${VTKGDCM_NAME}Python MODULE ${VTKGDCM_NAME}PythonInit.cxx)
SET_TARGET_PROPERTIES(${VTKGDCM_NAME}Python PROPERTIES
${GDCM_LIBRARY_PROPERTIES})
TARGET_LINK_LIBRARIES(${VTKGDCM_NAME}PythonD ${VTKGDCM_NAME})
FOREACH(c ${vtkgdcm_LIBS})
TARGET_LINK_LIBRARIES(${VTKGDCM_NAME}PythonD ${c}Python${DEXTENSION})
ENDFOREACH(c)
TARGET_LINK_LIBRARIES(${VTKGDCM_NAME}Python ${VTKGDCM_NAME}PythonD)
# Python extension modules on Windows must have the extension ".pyd"
# instead of ".dll" as of Python 2.5. Older python versions do support
# this suffix.
IF(WIN32 AND NOT CYGWIN)
SET_TARGET_PROPERTIES(${VTKGDCM_NAME}Python PROPERTIES SUFFIX ".pyd")
ENDIF(WIN32 AND NOT CYGWIN)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
