...
You can also create a custom .properties file and pass it to the cpptestcliwith the -settings switch. You can use the -settings switch multiple times to specify several .properties files. Entries with the same key will be overwritten.
| Code Block |
|---|
cpptestcli -settings team.properties -settings project.properties -settings user.properties -config "builtin://Recommended Rules" -compiler gcc_3_4 -input cpptest.bdf |
| Info | ||
|---|---|---|
| ||
Use double backslashes to specify file paths in the .properties file on Windows. For example:
|
| Info | ||
|---|---|---|
| ||
We highly recommend that you use encoded passwords to ensure successful authentication and increase the level of security; see Creating an Encoded Password. |
Settings Hierarchy
General settings are applied in the following order:
[INSTALL_DIR]/etc/cpptestcli.properties: the base configuration file that should not be modified.[INSTALL_DIR]/cpptestcli.properties: the main configuration file you can use to specify your settings that map contains templates for commonly used settings (license, reporting etc.).[USER_HOME]/cpptestcli.properties: for your convenience, you can store the configuration file in your home directory to overwrite settings from the [INSTALL_DIR] (for example, to ensure your settings are not affected by reinstallations or updates).[WORKING_DIR]/cpptestcli.properties: for your convenience, you can store the configuration file in your working directory.- Custom settings passed with the command line switch
-settings path/to/settings.properties(e.g.,-settings ../settings.properties). - Custom settings passed with the command line switch
-property [key=value].
All of the above settings can be overridden by custom settings that are passed with command line switches (e.g. -report, -config).
Modifying a Single Property
...