On 03/17/2015 05:50 PM, Adam Strzelecki wrote: > Does this BYPRODUCTS extension landed into 3.2?
Yes. > is there any new POLICY to tell CMake to stop generating > implicit phony rules for Ninja as proposed in: Not yet. For out-of-source builds the only place that the phony rules can show up is for custom command dependencies in the build tree that are not the OUTPUT of other custom commands. With 3.2 now that list can be cut further by listing BYPRODUCTS for those custom commands that produce them. IIUC the remaining issue is that for in-source builds all the custom command dependencies on source files now get phony rules. We need a policy to drop this behavior altogether and ask that projects explicitly specify their BYPRODUCTS. Correct? 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
