MantisBT - VTK
View Issue Details
0012876VTK(No Category)public2012-01-26 12:112014-10-02 17:08
Samuel John 
Dave DeMarle 
highminorhave not tried
closedunable to reproduce 
5.8.0 
6.2.0 
Release
incorrect functionality
0012876: Building VTK. DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON and python wrapper
Homebrew builds all software packages in a <tempdir> and then moves it to, e.g. /usr/local/Cellar/vtk/<version>/... and /usr/local/lib/vtk is a symlink to that dir.

We use DCMAKE_INSTALL_NAME_DIR and DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON to get the final RPATH correctly written into the libs, even if we build in a <tempdir>.

Then, just during the "make install", we add the <tempdir>/build/bin to DYLD_LIBRARY_PATH and that used to work well (before), since the freshly built libs can find each other.

Unfortunately, now we get the error:

make install
[...]
Linking CXX executable ../../bin/vtkpython
[ 95%] Building CXX object Infovis/CMakeFiles/vtkInfovisPythonD.dir/vtkRISReaderPython.cxx.o
[ 95%] [ 95%] Building CXX object Infovis/CMakeFiles/vtkInfovisPythonD.dir/vtkRandomGraphSourcePython.cxx.o
Building CXX object Infovis/CMakeFiles/vtkInfovisPythonD.dir/vtkRandomLayoutStrategyPython.cxx.o
ld: file not found: /usr/local/Cellar/vtk/5.8.0/lib/vtk-5.8/libvtkDICOMParser.5.8.dylib for architecture x86_64
collect2: ld returned 1 exit status
[ 95%] make[2]: *** [bin/vtkpython] Error 1
make[1]: *** [Wrapping/Python/CMakeFiles/vtkpython.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Obviously, some make target associated with python wrapping already expected the a dylib at the target install location (where it is not yet).

Now to my before-mentioned, ugly work-a-round:
Is there a better way than to introduce a temporary symlink: /usr/local/Cellar/vtk/5.8.0/lib/vtk-5.8 ---> <tempdir>/build/bin ???
I put this symlink, then "make" then remove that symlink, then "make install". Seems to work. Python can import vtk.
hackaton
Issue History
2012-01-26 12:11Samuel JohnNew Issue
2012-05-24 07:48Samuel JohnNote Added: 0028638
2012-05-24 07:48Samuel JohnNote Edited: 0028638bug_revision_view_page.php?bugnote_id=28638#r448
2013-06-25 16:39Dave DeMarleNote Added: 0031075
2013-08-14 17:05Dave DeMarleAssigned To => Dave DeMarle
2013-08-14 17:05Dave DeMarleStatusbacklog => active development
2014-09-30 10:44Dave DeMarleTag Attached: hackaton
2014-10-01 12:40Berk GeveciStatusactive development => backlog
2014-10-02 17:07Dave DeMarleNote Added: 0033548
2014-10-02 17:07Dave DeMarleStatusbacklog => closed
2014-10-02 17:08Dave DeMarleResolutionopen => unable to reproduce
2014-10-02 17:08Dave DeMarleFixed in Version => 6.2.0

Notes
(0028638)
Samuel John   
2012-05-24 07:48   
Applies to 5.10.0, too

(0031075)
Dave DeMarle   
2013-06-25 16:39   
Mind trying 6.0.0? If still there I will put it in the queue for 6.0.1.
thanks
(0033548)
Dave DeMarle   
2014-10-02 17:07   
Sorry, I tried to reproduce this, and the install appeared to work for me.

Much has changes in the cmakescript, I expect part of modularization or perhaps the removal of setup.py fixed it.