On 06/06/2014 01:20 PM, Brad King wrote: > The fundamental problem is Ninja's stat-then-build design. > They do have "restat" to declare that the output files should be > re-checked after a rule is run. We need a way to say that a > rule's input dependencies should be restat-ed after its > order-only dependencies are satisfied and up to date.
With a bit more information from project CMake code, it should be possible to generate a working ninja build system. See my explanation here: Add explicit specification of custom command side effect outputs http://www.cmake.org/Bug/view.php?id=14963 -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/cgi-bin/mailman/listinfo/cmake-developers
