Brad King wrote: > On 12/01/2014 12:04 PM, Bill Somerville wrote: > > One thing that looks suspicious are the lines mapping words to content > > > > along the lines of : > > arg [-lmingw32] ==> lib [mingw32] > > arg [-lgcc] ==> lib [gcc] > > arg [-lgcc_eh] ==> lib [gcc_eh] > > > > which in 3.1 look like this: > > arg [-lmingw32] ==> lib [] > > arg [-lgcc] ==> lib [] > > arg [-lgcc_eh] ==> lib [] > > > > I'm not sure where they are generated. > > That looks like a regression only in construction of the log messages. > I've fixed that here: > > CMakeParseImplicitLinkInfo: Fix implicit library logging > http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=20bf6971 > > and will include it in the next 3.1 release candidate.
Can't CMAKE_MATCH_1 be used twice? Otherwise the "lib" variable should explicitely be unset, the name is much too generic to not be reused by someone perhaps wondering about the content already in there. Eike -- -- 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
