Setting Environment Variables

Command Line Interface

The command line interface (CLI) tools require several environment variables to be set.

These variables determine, for example, the Target Deployment Port (TDP) that you are going to use. The available TDPs are located in the product installation directory, under targets. Each TDP is contained in its own sub-directory.

Prior to running any of the CLI tools, the following environment variables must be set:

You must also add the product installation bin directory to your PATH.

Note   Some command-line tools may require additional environment variables. See the pages dedicated to each command in Reference section of the help.

Note   Environment variables concerning Java on Windows must not contain spaces. Use 8.3 naming conventions, for example: TESTRTDIR=C:\PROGRA~1\HCL\TESTRE~1.

Most of these environment variables are set during installation of the product. Under Linux, use the testrtinit.sh script to set these variables. See the Reference section for more information about these scripts.

Automated Testing

If you are using Component Testing or System Testing features, the following additional environment variables must be set:

Library Paths

UNIX platforms require the following additional environment variable:

where <platform> is the hardware platform and <os> is the current operating system.

Example

The following example shows how to set these variables for OneTest Embedded with a sh shell on a Suse Linux system. The selected Target Deployment Port is clinuxgnu.

TESTRTDIR=/opt/HCL/TestRealTime.v2002R2

ATCDIR=$TESTRTDIR/bin/intel/linux_suse

ATUDIR=$TESTRTDIR/lib

ATS_DIR=$TESTRTDIR/bin/intel/linux_suse

ATLTGT=$TESTRTDIR/targets/clinuxgnu

ATUTGT=$TESTRTDIR/targets/clinuxgnu

LD_LIBRARY_PATH=$TESTRTDIR/lib/intel/linux_suse

PATH=$TESTRTDIR/bin/intel/linux_suse:$PATH

export TESTRTDIR

export ATCDIR

export ATUDIR

export ATS_DIR

export ATLTGT

export ATUTGT

export LD_LIBRARY_PATH

export PATH