Compiling the Test Harness

Command Line Interface

Each of the Test Script Compilers converts a test script into test harness source code. This section explains how to compile the test harness source file.


In order to compile a generated source file, you must check that:

  • A working C, C++ or Ada compiler is installed on your system

  • If you are using System Testing, you have prepared a valid options.h file

  • If you are compiling on a target different from the host where the file was generated, the generated file must have been produced using the -NOPATH option (available with every Test Script Compiler), and the /lib sub-directory of the Target Deployment Port directory must be copied onto the target.


If you are using Component Testing, System Testing or Component Testing for C++ alone without any of the runtime analysis tools, then simply compile the generated test harness source file with your C or C++ compiler.

If you are compiling on a remote target, do not forget to add to the include search path the /lib sub-directory that you have copied onto the target.

If you are using SCI instrumentation features (Memory Profiling, Performance Profiling, Code Coverage, Runtime Tracing and C++ .otc contract check), use the specific command line options for the Instrumentor in the Reference section:

Related Topics

Instrumenting and Compiling the Source Code | Command Line Interface