[CMake] Python version specification in FindPythonInterp is ignored

[Ateljevich, Eli]

Actually, clearing the cache worked for FindPythonInterp but I still can't get FindPythonLibs.cmake to work. Same problem .... it can find the 2.4 version but not the 2.7 version - and gives an error when 2.7 is required. Obviously, I cleared the cache this time. Again, is there a hint I can give to help it find the version I want?

I am on linux, by the way. Most of what I see there seems to be for Windows. Any clues?

Eli

From: Ateljevich, Eli
Sent: Monday, June 25, 2012 1:54 PM
To: Ateljevich, Eli; cmake at cmake.org
Subject: RE: Python version specification in FindPythonInterp is ignored

Apologies to all. It worked OK after I blew away the cache.

From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On Behalf Of Ateljevich, Eli
Sent: Monday, June 25, 2012 1:40 PM
To: cmake at cmake.org
Subject: [CMake] Python version specification in FindPythonInterp is ignored

Hi,
I am working with cmake 2.6 but have grabbed FindPythonInterp.cmake and its dependencies from 2.8.8. From what I can tell, this version is touted as having resolved most issues with specifying the python version.

Our OS has a python 2.4 called "python" installed in /usr/bin. There is another python 2.7 also called "python" we all load from the local module system. The 2.7 version is ahead of the 2.4 on path ... I have verified that the command line "which python" gives the path to the 2.7 version.

FindPythonInterp seems to find the 2.4 version no matter what I write. If I write: find_package(PythonInterp 2.7 REQUIRED) cmake will realize this is wrong and indicate an error, but it doesn't keep looking. I am trying to come up to speed, but I can't quite make out from the script what hint I might need to supply for FindPythonInterp.cmake to find the 2.7 version.  Can anyone help me out?

Thanks,
Eli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120625/864949da/attachment-0001.htm>