[vtk-developers] FindPythonLibs.cmake removal and OS X woes

Marcus D. Hanwell marcus.hanwell at kitware.com
Fri Dec 18 15:12:19 EST 2009


On Friday 18 December 2009 10:48:00 David Gobbi wrote:
> On Fri, Dec 18, 2009 at 8:15 AM, Marcus D. Hanwell
> 
> <marcus.hanwell at kitware.com> wrote:
> > On Friday 18 December 2009 07:58:51 David Gobbi wrote:
> >> The FindPythonLibs.cmake that comes with cmake has some obnoxious code
> >> that is breaking my build.
> >>
> >> To build against a particular version of the python framework, I use
> >> the following:
> >> PYTHON_LIBRARY:FILEPATH=/System/Library/Frameworks/Python.framework/Vers
> >>ion s/2.5/Python
> >>
> >> The FindPython module sees this, says "aha! you are using a
> >> framework!" and it resets the variable to this:
> >> PYTHON_LIBRARY:FILEPATH=-framework Python
> >>
> >> This is a problem that was fixed in VTK/CMake/FindPythonLibs.cmake a
> >> long time ago, but it seems that the fix was never propagated back to
> >> CMake.  Until it is, can VTK go back to its old FindPythonLibs?
> >
> > I didn't realize that changes like this had not been merged into CMake,
> > and was working on reducing code duplication. The new CMake comes with a
> > fix for finding the shared library on some Linux distributions, I will
> > merge these changes into the VTK version of the file and add it back to
> > VTK.
> >
> > I will also look at integrating the VTK changes into the CMake module for
> > 2.8.1 so that others can benefit from the fix.
> 
> Thanks.  I looked through all the other cmake "FindXXX" out of
> paranoia, and it looks like FindPythonLibs.cmake is the only one that
> is afflicted by this problem.
> 
Thanks for the help in testing the module with changes to fix up the 
frameworks issue David. I have committed an updated find module that should 
fix this issue in VTK.

Please let me know if you see any further issues.

Marcus
-- 
Marcus D. Hanwell, Ph.D.
R&D Engineer, Kitware Inc.
(518) 881-4937



More information about the vtk-developers mailing list