Compilation errors window
René J.V. Bertin
rjvbertin at gmail.com
Fri Jan 27 11:22:47 UTC 2017
On Friday January 27 2017 13:43:17 Aleksey Midenkov wrote:
> Maybe I am too concise in my statements and not well understood? I
> want compilation messages (errors, warnings and notes) be filtered out
> and placed in separate error list. This list is expected to be the tab
> in Problems window (Errors tab near Parser tab). Further it is
> expected to filter out by severity, sort by text/location, group by
> message text, etc. Can KDevelop do it?
The Problems tab shows output from the parser and from any supported analysers, tools you can run without (or before) doing an actual build. Given that the parser is based on Clang that already gives you most errors that compiler would give you.
I think that compilation errors should go into the build view. You have a point that the build output that this could be better organised.
Apple's Xcode gives a good example of what I'd like to see, which is very close to how results are displayed in the "Find/Replace in Files" toolview (but everything collapsed by default). You get just a list of the files that were compiled, with tiny counters showing the number of warnings and errors, and a thingy to uncollapse each line to show the actual compiler output.
But Xcode will use only handful of known compilers, so it has much more knowledge of the compiler output format that has to be parsed. KDevelop works with multiple build systems each of which work with just about any number of compilers and can add their own filtering of the output.
But: patches welcome, I presume :)
More information about the KDevelop