This topic provides information about integrating C/C++test with Renesas RX.

Integration Overview

Both C/C++test standalone and the C/C++test Eclipse plugin allow C/C++test to be used with Renesas RX—no special integration is required, because C/C++test's support for Renesas RX does not involve integrating with the RX development environment. Instead, C/C++test is preconfigured to support RX set of compilers and allow C/C++test projects to use these compilers.

You can use the cpptesttrace utility to create a .bdf file based on an e2studio project (see Generating a .bdf File From an e2studio Project) and import the .bdf file into C++test for analysis (see Import BDF file into C++test).

Support Overview

See IDE Support for information about Renesas e2 Studio versions supported by C/C++test.

See Compilers for information about supported compilers.

Generating a .bdf File From an e2studio Project

  1. Start console.
  2. Renesas provides a bat script that sets the required environment variables. You can run this script after setting the correct "InstallDirectory" variable in
    <renesas_rx_installation_dir>\setccrx_sample.
    Otherwise, set the compiler required environment variables per the compiler documentation (BIN_RX, INC_RX, RXC_LIB, TCINSTALL, TMP_RX) and add the following locations to PATH:
    <renesas_rx_installation_dir>\bin.
  3. Set the C++test install directory on PATH.
  4. CD to the project's target configuration directory (<project_workspace_location>/<Debug or HardwareDebug>)
  5. Run the following command:
cpptesttrace --cpptesttraceProjectName=<prj_name>
--cpptesttraceOutputFile=<prj_dir>\<prj_name>.bdf
<path_to_e2studio>\e2_studio\Utilities\make.exe all

To enable logging, add the -d option after calling make.exe and before the all command.

Notes

Specify the absolute path to the --cpptesttraceOutputFile option. This is because several .bdf files are likely to spread through working directories spawned by Renesas RX toolchain commands. You may have to place quotation marks around the options containing spaces/braces.

By default, the trace feature is configured to capture each toolchain executable name recognized by C/C++test through built-in compiler configurations. If the process' command-lines aren't scanned, specify the compiler and linker executable names by adding a --cpptesttraceTraceCommand option to the cpptesttrace command. For example:

--cpptesttraceTraceCommand=ccrx\.exe$|rlink\.exe$

The cpptesttrace command always appends its output file, so you should remove the previous .bdf file before re-scanning the project.

Import BDF file into C++test

  1. Start console.
  2. Set environment for the appropriate toolchain as described in the documentation (executables on PATH).
  3. Start C++test.
  4. Follow steps of importing the BDF file described in documentation (see Importing project using Build Data File with the GUI wizard).
  5. Confirm project settings correctness in Properties> Parasoft> C++test> Build Settings.

You must repeat the entire process following any changes to the original project unless you are adding new sources in existing source locations.

  • No labels

Need assistance? Visit our support page