Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Creating a build specification

Creating the build specification is the first step in performing your analysis. The build specification contains detailed information about your build, and is used by the Klocwork analysis engine to perform analysis on your code. It is important that the build specification be as up to date as possible to ensure that your analysis is accurate and complete.

Build specification file format

The format of the build specification varies depending on the language of your source code. See the following table for more information:

Create the build specification

How you create your build specification depends on the language of your source code, though the process for each language is similar. See the following table for more information:

If you're analyzing mixed C/C++ and C# projects, see Analyzing mixed C/C++ and C-sharp projects.

For some projects, you may not be able to create a build specification using one of the methods defined above. For these cases, you can use kwwrap to generate a build trace file, and kwinject to generate a build specification.