Closed MarkoSagadin closed 11 months ago
Progress report:
.xml
files. Shouldn't be too hard.compile_commands.json
file, which we already generate in our builds. It is also a better way if we manually stitch together CodeChecker commands, as we have better control of input parameters.Possible workflows with CodeChecker:
Implementation
The question that I had to resolve was: how to integrate the CodeChecker into the developer's workflow? Should I just write some scripts and make the invokeable from the Makefile that is in the root directory? Or should I integrate it into the East?
After some consideration, I have decided to integrate the CodeChecker into East:
This is great!
Is it firefox only or any browser?
This can of course be made configurable.
Context
CodeChecker is a static analysis infrastructure built on the LLVM/Clang Static Analyzer toolchain. It can scan your codebase with a three different tools (cppcheck, clangsa and clang-tidy) and produce report documents. This report document show what possible errors and mistakes are in your code.
The best part is that the CodeChecker also includes a web server component (demo), where you view the reports in a nice format and keep a track of the old and new bugs.
CodeChecker is now a part of the upstream Zephyr, so now is ideal time to include this tool in our projects.
Required steps / Implementation details
Definition of Done
Above is done and created documentation and code are reviewed.