Instrumenting and Compiling the Source Code
Command Line Interface
3. Open
products.h or Products.java in a text editor and add the following
define
at the beginning of the file:
4. #define
ATL_WITHOUT_STUDIO
5.
Make any necessary changes by adjusting the corresponding macros in the file.
The product_model.h file is self-documented, and you can adjust every macro to one
of the values listed. Each macro is set to a default value, so you can keep everything
unchanged if you don't know how to set them.
Note Pay attention to correctly set the macros starting with USE_, because
these macros set which features of Test RealTime you are using. Certain
combinations are not allowed, such as using several test features
simultaneously.
Ensure that the ATL_TRACES_FILE macro correctly specifies the name of the trace
file which will be produced during the execution. If you are using Component
Testing, this value may be overridden by a Test Script Compiler command line
option.
Take note of the directory where this file is stored, you will need it in order to
compile the generated or instrumented source files.
Instrumenting and Compiling the Source Code
The runtime analysis features (Memory Profiling, Performance Profiling, Code
Coverage and Runtime Tracing) as well as Component Testing for C++ Contract
Check all use SCI instrumentation technology to insert analysis and SCI dump
routines into your source code.
Requirements
Before compiling an SCI-instrumented source file, you must make sure that:
·
A working C, Ada, C++ or Java compiler is installed on your system
·
If you use Component Testing for C++, you have prepared a valid options.h file
·
If you compile on a target different from the host where the generated file has
been produced, the instrumented file must have been produced using option -
NOPATH, and the sub-directory lib of the selected Target Deployment Port
directory must be copied onto the target.
There are two alternatives to instrument and compile your source code:
·
Using the Instrumentation Launcher in your standard makefile
·
Using the Instrumentor and Compiler separately.
Instrumentation Launcher
327
