Including ccc-analyzer build warnings in scan-build report

Currently developers must manually scan the (usually rather verbose) output of scan-build to find any build warnings which are given by ccc-analyzer during build since they're excluded from the scan-build report. Is it be possible to include those build warnings into scan-build report?

- Nikita

Hi Nikita,

This is a good idea and something Ted and I have discussed. I believe that Ted has the logs so that it is easy to collect the data, but the blocking issue was how to present this in the UI (there are still a number of cases where clang emits bogus warnings, sometimes in large numbers). However, it is something we want to do to increase the visibility of clang’s warnings and hopefully iron out the bogus warnings faster. Mostly we just need someone to take it on.

  • Daniel