MantisBT - VTK
View Issue Details
0011869VTK(No Category)public2011-02-16 14:252016-08-12 09:55
thorbenk 
David Partyka 
normalminoralways
closedmoved 
Gentoo Linux~amd64
 
 
0011869: build system fails to find correct sip.h even though SIP_INCLUDE_DIR is set
I had to build my own sip, which I installed in a prefix in my home directory. I set the SIP_EXECUTABLE, SIP_INCLUDE_DIR and SIP_PYQT_DIR variables, but still cmake picked up the wrong SIP header, which resulted in a compiler error. Once I had uninstalled my system's sip-dev package, building vtk worked.
No tags attached.
Issue History
2011-02-16 14:25thorbenkNew Issue
2011-02-16 14:26David PartykaAssigned To => David Partyka
2011-02-16 14:26David PartykaStatusbacklog => tabled
2011-02-16 15:19David GobbiNote Added: 0025449
2013-07-22 20:33Dave DeMarleStatusbacklog => expired
2013-07-22 20:33Dave DeMarleNote Added: 0031289
2016-08-12 09:55Kitware RobotNote Added: 0037221
2016-08-12 09:55Kitware RobotStatusexpired => closed
2016-08-12 09:55Kitware RobotResolutionopen => moved

Notes
(0025449)
David Gobbi   
2011-02-16 15:19   
This issue has been discussed on the mailing list, for example:
http://www.vtk.org/pipermail/vtkusers/2010-September/112011.html [^]
The sip-dev package does not "play nice" with user-built sip packages, so having the user uninstall it is probably the wisest solution.

The problem is that the sip-dev package installs sip.h directly in python's main include directory. Setting SIP_INCLUDE_DIR to somewhere else will not remove the python include dir from the include path (it is pretty obvious why it can't). It might be possible to mess around with the order of include directories in CMake to make it work, but I believe that has already been tried and was not successful.
(0031289)
Dave DeMarle   
2013-07-22 20:33   
Dave P no longer works on the project. If these old issues still exist in 6.0.0, reopen them and assign to Dave DeMarle
(0037221)
Kitware Robot   
2016-08-12 09:55   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.