On 02/16/2016 01:42 PM, Greg Jung wrote: > A true MinGW wx-config should report Windows paths. > > Good point, which is why modifying wx-config is done. > MSYS/configure ... will build wx as if it knows nothing about > windows' paths and the wx-config output works as it should, > it is an MSYS weakness that fails in one aspect downstream > (I forget exactly what), the workaround is to make the paths > come out of wx-config in DOS format. Since this workaround > wasn't implemented until the more recent msys2 package builds > (which are compiled with a different compiler - worse possible headaches), > Simon worked a cmake fix. For my usage I've been editing wx-config.
Okay, I see that we are already handling this special case in FindwxWidgets.cmake by using "sh wx-config" in execute_process calls. This means the module is already aware that the wx-config it is running is not a Windows tool. The proposed change merely adds support for treating the output accordingly. I've applied the change with minor tweaks and tried to explain this in the commit message: FindwxWidgets: Resolve Cygwin/MSYS paths to Windows paths https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=843213d5 Thanks, -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
