On Fri, Feb 26, 2010 at 9:17 AM, Hendrik Sattler <p...@hendrik-sattler.de> wrote: > Zitat von Bill Hoffman <bill.hoff...@kitware.com>: > >> Noel O'Boyle wrote: >> >>> >>> Done. I've attached the result (off list). In summary it seems to be >>> searching for python2.6.exe first, instead of python.exe. >>> >> >> OK, so that is the problem.... >> >> It looks for names in this order: >> >> NAMES python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 >> python2.0 python1.6 python1.5 python >> >> >> It will prefer python2.6 over python in the PATH, and it has no way of >> knowing or caring if one is cygwin or not. I don't think there is much >> we can do about this. >> >> I should have noticed this: >> C:/Python26/python.exe >> C:/Cygwin/bin/python2.5.exe >> >> >> I suppose one fix could be to to have the windows one prefer python >> over any of the named version ones... > > Or find both independently and compare their versions. OTOH, the problem was > the library/executable mismatch, so it doesn't matter which is found as long > as the library matches the executable.
+1 There is an old bug report for cmake for this. PythonLibs should be derived from a python -c"..." (see bug #2257) Cheers -- Mathieu _______________________________________________ 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://www.cmake.org/mailman/listinfo/cmake
