It reminded me of the PPA with daily builds we have for Ubuntu [1], which I guess works as a continuous integration system building each revision. Since I don't think we should interfere with (read break :p) the existing one (which anyways builds using gcc), I guess we should attempt to set up an alternative one running clang/llvm with static code analysis. I have no idea how complicated this would be though.
The problem is of course whether anyone will look at these reports or not. Depending on the amount of issues, I think this might require some initial work in order to eliminate existing issues to keep new ones from drowning in the noise. We might want to consider creating a general bug report for errors found by the static analyser, attach new logs every couple of weeks (and comment notable changes).
Nicolai: I agree on both points.
It reminded me of the PPA with daily builds we have for Ubuntu [1], which I guess works as a continuous integration system building each revision. Since I don't think we should interfere with (read break :p) the existing one (which anyways builds using gcc), I guess we should attempt to set up an alternative one running clang/llvm with static code analysis. I have no idea how complicated this would be though.
The problem is of course whether anyone will look at these reports or not. Depending on the amount of issues, I think this might require some initial work in order to eliminate existing issues to keep new ones from drowning in the noise. We might want to consider creating a general bug report for errors found by the static analyser, attach new logs every couple of weeks (and comment notable changes).
[1]https:/ /launchpad. net/~widelands- dev/+archive/ widelands- daily