This section covers:

Recommendations

Testing VxWorks 653 projects is supported for the "Wind River GCC 3.3.x" compiler family.

A custom setup procedure should be applied for VxWorks 653 projects since these projects are not supported by the Wind River Workbench managed build system and C++test cannot use standard Workbench integration facilities for obtaining build information.

Configuring Projects for Testing

Follow the configuration description that best matches your current VxWorks 653 project configuration:

Wind River Workbench Project

If your VxWorks 653 project is configured as a Wind River Workbench project with a user-defined, makefile based build:

  1. Select Properties from the project context menu.
  2. Expand the  Parasoft> C++test category in the left pane.
  3. Select Build Settings.
  4. Set Options source to Use options from a build system.
  5. Modify the build command line if needed (you probably need to set the CPU, BSP, and PAR-TADDR attributes).
    • Command line example:
      make -f Makefile.wr CPU=SIMNT BSP=simpc PARTADDR=0x28000000 -i CXX=${CPPTEST_SCAN} CC=${CPPTEST_SCAN} LD=${CPPTEST_SCAN}
    • In general, this build command should correspond to the build command used for the original build, but the variable used for referencing compiler and linker should be substituted with the options scanner util.
    • See Creating a Project Using an Existing Build System for details.
  6. Under Compiler settings, select Wind River GCC 3.3.x Family.
  7. Close the properties window.

Notes

  • Part of a VxWorks 653 project source code is generated during the make build, and regenerated on each rebuild. These files are not visible in the Workbench project until you refresh it by selecting Refresh from the project context menu.
  • By default, a command line specified in "Build command line" contains the make -B option, which prompts make to unconditionally call all targets. C++test is using this flag to ensure that build flags from all targets will be collected. However, this flag can cause problems with VxWorks 653 make files (for example, endless looping of build process). To avoid problems with the build process and ensure that C++test will collect all necessary information from the build process, the following practice is recommended: Before the initial analysis or after any build system changes that may affect build flags set or build files set, call the "clean" target to ensure that the build run used for build options scanning will provide all necessary information. Optionally you can include the clean target at the beginning of the targets list in "Build command line".

    make -f Makefile.wr CPU=SIMNT BSP=simpc PARTADDR=0x28000000 -i CXX={CPPTEST_SCAN} CC=${CPPTEST_SCAN} LD=${CPPTEST_SCAN} clean all

Not a Wind River Workbench Project

If your VxWorks 653 project is not configured as a Wind River Workbench project, follow the standard procedure for importing a project through a build data file. For more details, see Using cpptestscan or cpptesttrace to Create a Build Data File. For example, to generate a build data file you may use a command similar to the following:

make CPU=PPC604 BSP=wrSbc750gx PARTADDR=0x40000000 CC="cpptestscan ccppc --cpptestscanOutputFile=D:/output.bdf --cpptestscanProjectName=HelloWorldFromBdf" LD="cpptestscan ldppc --cpptestscanProjectName=HelloWorldFromBdf --cpptestscanOutputFile=D:/output.bdf"

This will create a build data file called output.bdf and save it on disk D. The build data file can be used to import a project to C++test as described in Creating a Project Using an Existing Build System. Be sure to select the Wind River GCC 3.3.x compiler family by opening the C++test project properties panel, opening the Build Settings page, then selecting Wind River GCC 3.3.x for Compiler Settings: Family.

  • No labels

Need assistance? Visit our support page