Hi Kent, Matt started to work on a debugger last year, any contribution would be welcome. See https://github.com/thewtex/cmakedbg
Hth Jc On Thu, Feb 21, 2013 at 3:32 PM, Kent Williams <[email protected]>wrote: > As I'm now deep in tracing through 80K lines of cmake --trace output, man > I'd love some sort of CMake debugger! > > Actually if you use Emacs you can kinda sorta do tracing -- run CMake with > the --trace parameter in the compile bufffer (i.e. alt-x compile command) > and then the Emacs next-error steps a line at a time through the trace > output, just like a source debugger. > > But it doesn't give you the option of seeing the values of CMake > variables, or to change them. > > I know this is asking for a major feature change, but CMake has grown up. > We now have multi-thousand-line CMake build systems, and the only > debugging tool we have is MESSAGE() > > > -- > > 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 > -- +1 919 869 8849
-- 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
