In this section:

Installation

You can install C/C++test and its Parasoft DTP Plugin for Eclipse into the Wind River Workbench IDE. No specific actions are required. See Parasoft Plugin for Eclipse for details about installation.

Enabling and Configuring the DTP Engine

Follow the procedure described in Enabling and Configuring the DTP Engine. The following settings are recommended when specifying the command line parameters:

${scope} ${configuration} ${bdf} -compiler <compiler configuration> ${scope}

• The ${bdf} argument refers to the build data file generated during Wind River Project build process.
• The <compiler configuration> setting refers to the compiler configuration that corresponds to the compiler used for the project build. See Supported Compilers for a list of available compiler configurations.
  
  

Configuring Wind River Workbench projects for DTP Engine

You will need to customize some build settings for Wind River Workbench projects you are testing with Parasoft C/C++test via the DTP Plugin for Eclipse. Customization is necessary to extend the project build process so that the .bdf (build data file) can be generated. The .bdf is used as a supplementary input for the analysis run process (see Enabling and Configuring the DTP Engine).

Build customization includes settings for one more helper files, which are environment data files that serve as additional supplementary input for the analysis process.

Follow the procedure described in the sections below to customize build settings for the following types of Wind River Workbench Projects:

• Downloadable Kernel Module
• Real Time Process Application
• Relinkable Kernel Module
• Shared User Library
• Static Kernel Library
• Static User Library

Configuring BDF File Generation

1. Right click on a project and choose Properties to open the project properties panel.
2. Select the Build Properties category and click the Build Support and Specs tab.
   
       

3. In the Build command field, replace the %makeprefix% with the following command:

   [DTP engine install dir]/bin/cpptesttrace.exe --cpptesttraceEnvInOutput=yes --cpptesttraceEnvars=* --cpptesttraceOutputFile=../cpptest.bdf --cpptesttraceEnvFile=../cpptest.env

    Do not alter or remove the make --no-print-directory part of the command. The final command should read: 

   [DTP engine install dir]/bin/cpptesttrace.exe --cpptesttraceEnvInOutput=yes --cpptesttraceEnvars=* --cpptesttraceOutputFile=../cpptest.bdf --cpptesttraceEnvFile=../cpptest.env make -no-print-directory

      

Configuring Custom Build Target for BDF File Removal

1. Right click on a project and choose Properties to open the project properties panel.
2. Select the Build Properties category and click the Build Rules tab.
   
3. Click New to add a custom build target.
4. Specify a name for custom build target, e.g., "remove BDF file".

5. Enter the following command line into the Make rule or command field:

   rm -f %selected_project_location%/cpptest.bdf %selected_project_location%/cpptest.env

6. Choose Command from the Type drop-down.
   
7. Click OK to confirm your settings.

The .bdf file is updated with every build action; old content is not removed. The "Remove BDF file" Custom build target can be used to remove the .bdf from the project, which may be required if the .bdf becomes too large. If removed, the .bdf must be regenerated before running the next code analysis session.

Optimizing the BDF Generation Process

One-time Generation

If your project changes infrequently, i.e., new files are rarely added or compilation options rarely change, you can optimize the .bdf generation process by performing a one-time generation.

1. Follow the steps described in Configuring BDF File Generation.
2. Perform "clean-rebuild all" cycle.
3. When a full rebuild is complete, the .bdf will be generated for the project and you can revert the modifications done to build settings.