Aleix Pol wrote: > I just pushed my change into a github clone for easier testing and > reviewing. https://github.com/aleixpol/CMake
Hi Aleix, Thanks for your efforts. Here are some things that are required before a feature like this can be committed to the cmake repo: * Discuss the feature with collaborators on the mailing list. * Design the feature. Determine at least the following: * Target use cases * How files are produced * What files are produced * Features required by various tools and IDEs * What is in the files * What is not in the files * Why ^ * Write documentation describing the file format and how to consume it. * More exact unit testing * Unit testing for 'interesting' cases. * Implement the feature satisfying the design for all of the targets IDEs and all relevant features of CMake. * Testing with existing third party cmake-using projects. All of the above must be done before cmake can accept a branch implementing metadata generation. Because this is important to get right, and because it requires up-to-date knowledge of the current cmake implementation and features in the master branch, I'm going to take over the 'ownership' of this feature and drive it myself. I'll start soon by creating a new mailing list thread to determine the design of the feature in collaboration with you, Tobias and Anton. We can iterate on the design, tests and implementation until it is complete. Thanks, Steve. -- 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