In version 9.4, a semi-automatic approach was added to improve the way the Checkmarx C++ parser handles macros and build files. This section provides a high-level description of what is offered.

Overview

The objective was to reduce the manual work of configuring a CppDefaultMacros.json file for each project being scanned, by providing the following:

• A method of inspecting and extracting macros, including paths and other information from the build files present in the project being scanned.

• A method of extracting macros from different repositories and adding them to a database to be used during the C++ preprocessing.

Open

C++ Build Files Support

The new approach includes elementary support for the most common C++ build files.

Currently, the following files/build technologies are detected:

• Makefiles

• CMake

• Autotools

• QMake

• Compile Database

We inspect these files to extract (when possible):

• Macro Definitions

• Global Include paths

• Target OS Architecture Information

• Other specific options, such as trigraphs

C++ Macros Database

The C++ Macros Database gathers C++ macros and their definition to be used in the CxSAST scans.

This database is shipped with the CxSAST solution with a pre-defined set of macros found on known and most-used libraries.

However it can be extended and fine-tuned for the customer (with the help of Checkmarx’s PS people), considering libraries present in the customer code base, which may not be on our database.

Supported Libraries (pre-defined set)

FAQ

Q: Is the CppDefaultMacros.json configuration file needed?

A: No. It is still considered in case it exists at the root of the project. The file is useful if want to add some extra information that is neither in the macro database nor in the build files.

Q: Are the build files processing ON by default?

A: Yes!