> > As a reminder, another branch of this discussion is pending over here: > > > http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/13948/focus=13982
That devolved into another issue. This also applies to msys-1 with a targetted python installation. I don't think there are any "structural" issues in running the mingw-w64/msys2 system using "MSYS Makefiles". The cmake adapted to running posix-mode msys2 is another matter. On Wed, Sep 2, 2015 at 6:02 AM, Brad King <[email protected]> wrote: > On 09/02/2015 07:13 AM, Ray Donnelly wrote: > > On Wed, Sep 2, 2015 at 10:33 AM, Greg Jung <[email protected]> wrote: > >> To revive this issue, I show a comparison of the CMakeCache entries for > >> cmake run from the same configuration, 1) cmake 3.2.3 with "old" > PythonLibs > >> .vs. 2) cmake 3.3.1 with the new FindPythonLibs.cmake. > > As a reminder, another branch of this discussion is pending over here: > > > http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/13948/focus=13982 > > -Brad > >
-- 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-developers
