[Cdash] Adding support for "Krazy" code checker to cdash ?

[Alexander Neundorf]

On Tuesday 30 March 2010, David Cole wrote:
> The easiest way is probably:
>
> - Set CTEST_BUILD_COMMAND to the command line that should be executed as
> the build step.
>
> - Use a CTestCustom.ctest to set CTEST_CUSTOM_WARNING_MATCH
> and/or CTEST_CUSTOM_ERROR_MATCH to lists of regular expressions that match
> the output of krazy.

The generated warnings from krazy already look like compiler warnings, so I 
guess ctest/cdash will be able to parse them.

> The second easiest way is to do what kwstyle does and write your own
> Build.xml that describe the errors and warnings precisely as you want.
>
> I'd answer more thoroughly, but at this point, for me, it's a code-analysis
> job depending on which route you take. (The knowledge is not just in my
> head/easily accessible, I'd have to go derive it from the source...) Since
> these are all open source things, you can do that just as easily as I can.

Ok. I'll have a look at the ctest_build() command and see what I can do there.

Alex