Building projects: undocumented build commands

[esbena]

For an analysis tool that needs to build a project before it can be analyzed, it may be a problem if the project has non-standard build commands that can not simply be guessed by the analysis tool.

This is be fine if you are interested in evaluating the tool's out-of-the-box abilities.

Alternatively, we could have a field in the benchmark entry that specify the standard way to build the project. Drivers can then use that information to build the project appropriately.

{
    "CVE": "CVE-YYYY-XXXX",
    "build-command": "./configure && make && make install",
    ...
}