[cmake-developers] [PATCH] FindPythonLibs repaired for MINGW -vs- WIN32 version confusion

Greg Jung gvjung at gmail.com
Wed Sep 2 15:06:01 EDT 2015


>
> 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 <brad.king at kitware.com> wrote:

> On 09/02/2015 07:13 AM, Ray Donnelly wrote:
> > On Wed, Sep 2, 2015 at 10:33 AM, Greg Jung <gvjung at gmail.com> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20150902/db3a7905/attachment.html>


More information about the cmake-developers mailing list