On Mon, Aug 26, 2013 at 12:32 PM, Robert Maynard <robert.mayn...@kitware.com> wrote: > I am able to replicate this problem with the 2.8.12rc1. Are you able > to construct a minimal test case so I can dig into why this is > happening?
Robert, So far I haven't had much luck creating a minimal test case, but I think I've pinpointed the change that introduce the observed behaviour: cmMakefile: Track configured files so we can regenerate them (#13582) ad502502dfee281e5b0ad8ac57057d72220b4380 It's parent, 4a6397a70c2b467b1285be4c0bae7533eb16f5e0, does not re-run ninja. I'll see if I can dig any deeper. -- 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://www.cmake.org/mailman/listinfo/cmake
