...
| Info | ||||
|---|---|---|---|---|
| ||||
In order to successfully analyze the source code, C++test needs to be started with the environment prepared for uVision compilation tools. The RVCT compiler and uVision debugger (Uv3.exe or Uv4.exe) locations have to be added to the $PATH variable before launching C++test GUI/CLI. The recommended practice is to use a uVision3-generated .bat build file for extracting the environment settings. |
Importing Keil uVision 4.0 Projects
| Anchor | ||||
|---|---|---|---|---|
|
To test code that compiles with the Keil 7.0 for C166 compiler, you must your Keil uVision 4.0 project
- Navigate to the project directory and run the following command:
[path to]\cpptesttrace.exe --cpptesttraceProjectName=[project name] --cpptesttraceOutputFile=[project name].bdf --cpptesttraceQuoteCmdLineMode=sq "[path to]\Uv4.EXE" -r [project file]- .Uv2 and .uvproj extensions are supported--the GUI will automatically convert .Uv2 projects
- cpptesttrace.exe is located within [INSTALL]\engine\bin\cpptesttrace.exe
- Default location of Keil Uv4.EXE gui is: "C:\Keil\UV4\Uv4.EXE"
- [project name] is a unique identifier for this project when it's imported to C++test
- Import the newly created .bdf using the C++test GUI
Fixing File Extensions or Keil C166 IDE-generated Source Files
The file extension case may change for some source files generated with the Keil C166 IDE. This will cause source file to be skipped during analysis.
...