On 9/24/2011 1:08 PM, Brian Davis wrote:
> 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.
What I would like to see at a minimum is a CMake Debugger showi
> 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.
What I would like to see at a minimum is a CMake Debugger showing a window
with the list of variables, not
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
On 2011-09-01 18:00-0400 David Cole wrote:
Sounds like a great research project for somebody. Would be cool to
see CMake options visualized for some larger projects...
Not sure of its feasibility in terms of completeness, however. I'm
sure you could come up with something rudimentary that seems
Sounds like a great research project for somebody. Would be cool to
see CMake options visualized for some larger projects...
Not sure of its feasibility in terms of completeness, however. I'm
sure you could come up with something rudimentary that seems to work
for some cases.
There are some cases
I was just replying to an acquaintance who was e-mailing me about CMake
configuration when I realized that CMake configuration options
which are only available depending on how other configuration
options are set could be analyzed/displayed using graph theory
(from a 5-minute study of graph theory
