Denis Barbier wrote:
On 2010/3/2 Michal Suchanek wrote:
On 03/02/2010 04:09 PM, Denis Barbier wrote:
On 2010/3/1 Michal Suchanek wrote:
[...]
[ 64%] Building CXX object ConnectVTKITK/CMakeFiles/_ConnectVTKITKPyt
hon.dir/ConnectVTKITK_wrapPython.o
Linking CXX shared module ../VolviewPlugIns/bin/_ConnectVTKITKPython.
so
/usr/bin/ld: cannot find -lvtkCommonPython
There is libvtkCommonPythonD so I am wondering if some cmake voodoo
failed to determine the correct library name or there is a symlink
missing.
vtkCommonPython and vtkCommonPythonD are different things, the former
is located at /usr/lib/pyshared/python2.5/vtk/libvtkCommonPython.so
Yes, I found the libraries in pyshared and linked them to /usr/lib and now
the build works.
I am still not sure if cmake should have figured out to include
-L/usr/lib/pyshared/python2.5/vtk/ and if so why it did not or if these
symlinks should have been installed.
I do not remember exactly how these libvtk*Python.so libraries are
generated upstream, I guess that they are generated along with
non-wrapped libraries libvtk*.so, and are thus found by
InsightApplications. But this is wrong, InsightApplications should be
told how to look for libvtk*Python.so into Python modules path. There
is some discussion about cmake and python at
http://www.itk.org/Bug/view.php?id=2257
According to /usr/share/doc/python-support/README.gz, Python
extensions under /usr/lib/pyshared are copied into /usr/lib/pymodules
where they can be found by python, and indeed
$ python -c 'import sys;print sys.path'
lists '/usr/lib/pymodules/python2.5'. Maybe a solution would be to
look for libvtkCommonPython.so in 'vtk' subdirs of all paths listed in
sys.path?
Anyway I am afraid that there is nothing to be done in python-vtk,
maybe this bug can be closed?
IMHO bugs should be closed only when they are fixed or when it is
determined that observed behaviour is expected and correct. If this is
not an issue with vtk but it is an issue with cmake then this should be
reassigned to cmake.
If the upstream bug report (which seems slightly different to me)
includes this issue then it should perhaps be marked as forwarded.
Thanks
Michal
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
