C++test's built-in GUI-based EW project importer only supports EWARM projects, and only for specific EWARM versions (see Support Overview). Importing EW projects for other toolchain versions or target architectures must be done with the
cpptesttrace utility. The
cpptesttrace utility scans the command lines for processes spawned by the
The importing process consists of two stages: 1) Generating the Build Data File (.bdf) and 2) importing this file in C++test.
cpptesttrace --cpptesttraceProjectName=<prj_name> --cpptesttraceResponseFileOption=-f --cpptesttraceOutputFile=<prj_dir>\<prj_name>.bdf iarbuild <prj_name>.ewp -build <EW_project_config_name>
Use an EW project configuration name (e.g.,
DebugRunFromFlash, etc.) for the
Specify the absolute path to the
--cpptesttraceOutputFile option. This is because several .bdf files are likely to spread through working directories spawned by
iarbuild toolchain commands.
You may need to place quotation marks around the options containing spaces/braces.
In most circumstances, you should name your C++test project after the .ewp file name when using the
By default, the trace feature is configured to capture each toolchain executable name recognized by 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 always appends its output file, so you should remove the previous .bdf file before re-scanning the project.
You may also use
-log all after the
-build flag to show detailed build progress information. The
-log all option is an
You must repeat the entire process following any changes to the original project unless you are adding new sources in existing source locations.