Roger Leigh wrote: > I thought using FindPythonInterp would be more portable than > simply invoking "python" directly (i.e. using $PYTHON_EXECUTABLE). > However, this does not appear to be the case. I'd be interested to > know if this is intentional or if I'm doing something wrong. > > I've tried using "find_package(PythonInterp 2.6.0 REQUIRED)" on a > variety of systems. The software in question works with any > python 2.6 or 2.7 version. > > On Debian, with the default python 2.7 installed, it picked up > python 2.6.8 (from python2.6-minimal) which lacked all the > required modules. /usr/bin/python was 2.7 and matched the > version requirement, and had all the required modules > available.
In case you want the newest version of any Python major, as in your case, try find_package(PythonInterp 2 REQUIRED). But you are right, this would also successfully return you a 2.5. Greetings, Eike --
signature.asc
Description: This is a digitally signed message part.
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
