warning: symbol _ZN13vtkPythonUtil20GetObjectFromPointerEP13vtkObjectBase [...] found in none of the libraries about vtk-dicom HOT 8 CLOSED

In case this is not clear: libvtkDICOMPythonD.so.0.5.0 is underlinked with vtk 5.8 on my side.

from vtk-dicom.

I've pushed a fix that links vtkPythonCore (or, with vtk6, vtkWrappingPythonCore).

from vtk-dicom.

Better but now it is missing the python symbols:

$ nm -D ./obj-x86_64-linux-gnu/lib/libvtkDICOMPythonD.so.0.5.0 | grep Py
U PyBool_FromLong
U PyDict_SetItemString
U PyErr_Occurred
U PyFloat_FromDouble
U PyInt_FromLong
U PyLong_FromLongLong
U PyLong_FromUnsignedLong
U PyModule_GetDict
U PyString_FromString

from vtk-dicom.

you need to find_package(PythonLibs) + target_link_libraries(... ${PYTHON_LIBRARY})

from vtk-dicom.

I've added the python library to target_link_libraries. It was already being linked on OS X, but it had been omitted on UNIX for historical reasons.

from vtk-dicom.

that only provide the vtkpython symbols. Pay attention that on debian you dont get transitive linking for free. The current (git master) list of undefined symbols is:

dpkg-shlibdeps: warning: symbol PyErr_Occurred used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol PyString_FromString used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol PyBool_FromLong used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol PyFloat_FromDouble used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol PyLong_FromLongLong used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol Py_FatalError used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol PyModule_GetDict used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol PyDict_SetItemString used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol Py_InitModule4_64 used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: symbol _Py_NoneStruct used by debian/python-vtk-dicom/usr/lib/x86_64-linux-gnu/libvtkDICOMPythonD.so.0.5.0 found in none of the libraries
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to see them all)

from vtk-dicom.

Rather than directly use find_package(PythonLibs), I've decided to load it via vtkWrapPython.cmake, just like VTK itself:

set(VTK_WRAP_PYTHON_FIND_LIBS ON)
include(${VTK_CMAKE_DIR}/vtkWrapPython.cmake)

I chose to do it this way because vtkWrapPython.cmake has some special logic for dealing with debug libraries on Windows.

from vtk-dicom.

closing.

from vtk-dicom.