Indeed, I should have looked at the most recent version instead of this old patch found in the bug tracker. That module looks great.
On Thu, Apr 12, 2012 at 12:34 PM, Rolf Eike Beer <e...@sf-mail.de> wrote: > Am Donnerstag, 12. April 2012, 11:57:10 schrieb Andreas Schuh: >> Hi CMake folks, >> >> I run into a problem with CMake 2.8.4 which relates to the bug >> http://public.kitware.com/Bug/view.php?id=12338 . In particular, the >> issue that not the default python executable was found, but the most >> recent version that is installed. Thus, before noticing that this >> seems to be fixed in CMake 2.8.6, I implemented my own >> FindPythonInterp.cmake module for a project I am working on. >> >> As the new implementation also considers the PythonInterp_FIND_VERSION >> and PythonInterp_FIND_VERSION_EXACT variables, I thought it might >> still be of interest for future CMake releases, either just as >> reference or to replace the current FindPythonInterp.cmake module in >> which case the copyright and license notices may be altered so it >> works for distribution as part of CMake. > > Please have a look on the version that is currently in the git repository and > which will be part of the upcoming 2.8.8 release (and is part of both release > candidates). It should have a pretty decent version selection that also allows > one to select either python 2 or python 3 as well as exact versions. > > Greetings, > > Eike -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers