[DRAFT] CodeChecker invocation for single compilation entry with customizable behaviour

[vodorok]

When prototyping the bazel integration for CodeChecker, the need emerged to have a CodeChecker analyze invocation, which produces the output to a single file, insted writing a group of files for the analysis. Bazel could invoke this command for every single compilation action (in an aspect).

The following is proposed:

The main difference compared to the standard analyze command would be:

• A direct compiler call, (as a string) could be specified in place of the compilation database. The following example demonstrates the usage.

CodeChecker analyze --compile-action “gcc something.c” --output-file something.plist

Only a singleoutput .plist file should be generated

• The path to this output file could be directly specified with the --otput-file option.
• no other files such as metadata.json, compiler_info.json should be generated

The compilation and analysis directory should be the current working dir of the CodeChecker invocation.

We should consider that there might be multiple analyzers.

• Create a "custom" plsit, containing the output of all analyzers, so we could identify the analyzer that produced the diagnostic message.

In this mode, there should not be any metadata or shared files created, instead a separate command should generate these, or compute them during store and parse.