C quality metrics (especially changed lines of code)

I am looking for a quick simple way to create very basic quality metrics for some C code being built within TeamCity.
A more complete answer is likely to setup Sonar, but all I need for now is lines of changed code per commit over time.

I suspect the "changed" part will require someone to hook into the TeamCity plugin API or alternatively maintain an external database of some sort.
Another approach would be some script that engages with source control directly itself (ClearCase :() and manages to do the fancy diff itself.
As long as the crude script spits out a few TeamCity service messages this could even be graphed within TeamCity.

What quick and easy solutions are available for doing static analysis of C code within TeamCity?

Please sign in to leave a comment.