> > 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. On Tue, Feb 16, 2016 at 10:22 AM, Brad King <[email protected]> wrote: > On 02/16/2016 01:16 PM, Greg Jung wrote: > > Simon is working on MSYS2 for a mingw build. The MSYS2-native CMake > > is a different beast, and wouldn't be producing mingw programs. > > Okay, then why do we need to support a MSYS2-native `wx-config` tool? > A true MinGW wx-config should report Windows paths. > > -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
