Configuration files you can edit
Do not edit any Klocwork configuration files not listed in the following table.
All configuration files used in Klocwork analysis must be UTF-8 encoded if they contain multibyte characters (for example, Japanese). If your configuration files contain multibyte characters, you must convert them before using them in Klocwork analysis. See kwconv. Migration of a projects_root to Klocwork automatically converts all user-editable configuration files in the projects_root to UTF-8.
| File name | Description | Purpose of file | Applying the file to Klocwork analysis | More information |
|---|---|---|---|---|
| .h | macro override file for C/C++ | a file that you can create and apply to Klocwork C/C++ integration build or desktop analysis, allowing you to suppress the expansion of specified macros, or to replace undesired macro definitions with more suitable ones | import into integration or desktop project; file is automatically synchronized to connected desktops | Tuning C/C++ analysis |
| .jkb | Java knowledge base file | allows tuning of Klocwork issue detection to your Java software project | import into integration or desktop project | Tuning Java analysis |
| .kb | C/C++ knowledge base file | allows tuning of Klocwork issue detection to your C/C++ software project | import into integration or desktop project | Tuning C/C++ analysis |
| kwfilter.conf | compiler mapping file for C/C++ | used during creation of a build specification by kwinject to determine what kind of filter to use for an intercepted command. | used automatically in integration build or desktop analysis | Compiler mapping file format (kwfilter.conf) |
| kwmysql.ini | Database Server configuration file | allows tuning of memory size and limits for very large projects | used automatically in integration build analysis | Improving database performance |
| .mconf | metrics thresholds configuration file | changes the thresholds at which Klocwork reports issues | import into integration or desktop project | Changing the thresholds for reported metrics |
| metrics.xml | metrics report configuration file | allows you to make custom metrics reports available in Validate. Located at <projects_root>/config/metrics.xml. | used automatically in integration build analysis | Customizing metrics reports in Validate |
| .out | build specification file | a structured log of your build that is used as the basis of your Klocwork project | pass to kwbuildproject | Creating a C/C++ build specification, Creating a Java build specification,Creating a C# build specification |
| .pconf | checker configuration file | allows you to enable, disable and organize checkers | import into integration or desktop project | Configuring checkers for the integration build analysis |
| .sow | source ownership file | associates the name of a person or group with a file or class of source code | import into integration project | Tracking issues by owner |
| .szt | size-of-types file | allows specification of the size of bytes of your built-in types, so that the "bytes of" metrics are correctly calculated | import into integration project | Specifying sizes for built-in types |
| .tpl | build specification template file | a version of build specification that uses variables for any paths that may differ on local machines where Klocwork analyses are run | import into integration project; file is synchronized to connected desktops | Providing a build specification template for your developers |
| .tconf | taxonomy configuration file | allows you to add new custom checkers to taxonomies or categories and to add reference information to existing checkers. | import into integration or desktop project | Configuring checkers for the integration build analysis |
| .ume | user-defined metrics file | allows you to define your own metrics, apply them to a specific source file or class, and report on them in Validate. A text file with the extension .ume. | import into integration project | Customizing metrics reports in Validate |