> This is the simplest solution for the upcoming 3.1 release because > it just restores behavior to what 3.0 does. I've done it here:
Okay. But still I feel like this is just workaround rather than solution for the problem. > This is not about supporting projects that do it wrong. Ninja > wants to know not just that a file is generated, but also *which* > custom command generates it. We have no interface for specifying > side-effect outputs whose timestamps do not need to be newer than > the inputs. Yes, it isn't about doing anything wrong, but to make projects building fine with Make build fine with Ninja too. And you are right here, we have no means for provide proper transition to remove this implicit compatibility layer. We lack OUTPUT for add_custom_target. I can work on OUTPUT support for add_custom_target if you want? Together with new POLICY it will make sense, unless you have other opinion on that. But I guess it won't make it to 3.1? > That is what this issue is about: > Add explicit specification of custom command side effect outputs > http://www.cmake.org/Bug/view.php?id=14963 Shouldn't it be called "Add explicit specification of custom TARGET side effect outputs"? --Adam -- 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
