You cannot specify more than one Microsoft Visual Studio project file per project. As a workaround, create a top-level solution or workspace file and use it to create your Klocwork project.

To generate a build specification for multiple .dsp or .vcproj files:

1. In Visual Studio, create a new workspace (solution) file and add your existing projects to it (.dsp or .vcproj files).
2. Make sure the settings are correct by building the Visual Studio project in Visual Studio. This ensures that your project is properly set up, and that any files generated "on the fly" are available to the Klocwork tools.
3. If necessary, define the dependencies between your projects. If there are dependencies, follow the dependency rules (for example, executable linking a static library depends on the static library). If the modules are independent, pick one project as the main project and make it depend on all the other ones.
4. Use kwdspparser or kwvcprojparser to generate a build specification.

This example uses Visual Studio 6 with the open-source project WinCVS.

To gather information about the WinCVS software system and create a build specification:

1. Change the working directory to the top-level source directory in WinCVS that contains the .dsp file. For example:

   cd C:\WinCvs2_0_2_4_Src\WinCvs
   

2. View a list of possible configurations with the --list-configs option of kwdspparser:

   kwdspparser <dsp-file> --list-configs
   

   For example:

   kwdspparser wincvs.dsp --list-configs
   

3. You see output resembling the following (after the copyright information):

   Processing "C:\WinCvs2_0_2_4_Src\WinCvs\wincvs.dsp"...

   Possible configurations are:

   - "Release"

   - "Debug"

4. Run the parser on the project file:

   kwdspparser <dsp-file> -c <config-name> [-o <output-file>]
   

   We'll use the Debug configuration in this example, and specify it with the -c option.

   We'll use the -o option to specify the name and location of the build specification file. By default, it is named <dsp-file>.out, and is saved in the current working directory.

   For example:

   kwdspparser wincvs.dsp -c Debug -o "C:\Program Files\Klocwork\projects_root\config\wincvs2_0_2_4.out"
   

5. Output resembling the following appears (after the copyright information):

   Processing configuration "Debug" in project "C:\WinCvs2_0_2-4_Src\WinCvs\wincvs.dsp"...

   The project's build specification has now been saved to the specified location.

kwvcprojparser and kwdspparser include support for Visual Studio built-in macros.

Visual Studio substitutes environment variables of the form $(VARIABLE). Built-in Visual Studio macros and environment variables are expanded in the same manner. Most of the built-in macros are directly supported by the parsers. In the unlikely case that you encounter an unsupported macro, you see a message like the following:

Processing configuration "Release|Win32" in project "f:\CVSREPOSITORY\Klocwork-HEAD\sources\remote_cxx\kwdistadmin.vcproj"... Warning: Environment variable "$(Klocwork_HOME)" is not set

In such cases, define this variable in your environment. The easiest way is to open a command prompt and issue the following command:

Set Klocwork_HOME=<your value>

The value of the variable depends on the usage.

In addition, the kwvcprojparser option /useenv instructs the parser to use the INCLUDE environment variable. Note that all paths specified in the INCLUDE environment variable are specified as "system includes" in the resultant build specification, and override any Visual Studio .NET 2003, 2005 or 2008 settings set in Tools > Options > Project > VC++ Directories.

Note that kwdspparser does not have this functionality, and always uses Visual Studio 6 settings.

Now that you've created a build specification, you're ready to run the C/C++ integration build analysis.