On 9/1/2011 8:48 PM, Alan W. Irwin wrote:
Yeah, it is fun to speculate about something new like this that would be of considerable benefit to help a project's developers and users visualize the complete set of options and their dependencies for their project's build system. Unfortunately I don't have sufficient knowledge of the CMake code base (or C++ for that matter) to do this myself, and I assume nobody at Kitware has spare time to do such an implementation. However, maybe someone else here or perhaps a GSOC student next year might be interested in fleshing this idea out into something useful.
I guess at the end of the day what you are talking about is a static code analysis tool for the CMake language. Those tools look at all possible branches of code and try to detect errors. Although not impossible, this would not be something that could be hacked out quickly. As a rough order, I would put this at several man months of effort. Maybe a GSOC...
-Bill _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
