Home
Download
Setup
Environment
|
Setup
The distribution file contains:
the RTIG (RTI Gateway), central RTI process
the RTIA (RTI Ambassador), local RTI component, there is
one RTIA process with each federate
the libRTI library : each federate is linked to this
library which provides HLA sercices.
The compilation directory is created when unpacking the tar
file. It can be located anywhere and is just used during compilation
and installation. Its name is certi-version, where
version has to be replaced with the actual version number.
The target directory : directory where files are
installed. The usual Unix sub-directories are used : bin,
lib, etc. This directory can be /usr or
/usr/local for system-wide installations, or
$HOME/CERTI in a user directory.
The execution directory contains the federation
files (.fed.). Programs (RTI and federates) are launched from
this directory
Usual untar command:
tar zxvf certi-version.tar.gz
If your tar doesn't accept the z option, first unzip the tar file with gunzip then untar with "tar xvf file.tar".
A directory named certi-version is then created.
First, the configuration script should be executed in the compilation directory. The syntax is :
env init ./configure
options where the optional env part is used to modify the environment during the compilation
Examples
./configure --prefix=$HOME/CERTI
env CC=gcc-3.0 CXX=g++-3.0 ./configure --prefix=/usr/local/certi
Remarks
Be careful, the local_config.hh, MessageBody.hh and SocketUN.hh files
include constants definitions, which must be updated
according to the applications needs (for example and respectively,
MAX_BYTES_PER_VALUE, BODY_BUFFER_MAX_SIZE, SOCKET_BUFFER_LENGTH).
Next, CERTI should be compiled from the compilation directory, type:
make
This next step copies files from the compilation directory to the installation directory (the one in the --prefix option). The command is:
make install
| Testing with « Billard » application
|
CERTI binaries and federates must appear in the PATH environment variable, so maybe you need to add directories to this variable:
export PATH=$PATH:$HOME/CERTI/bin
Programs can now be launched from the execution directory (the one with the .fed files. You need to have either the CERTI_HOST environment variable set to the name of the machine on which the RTIG is running, or the RTIA.dat file containing this name.
Example
In 4 different terminals :
export PATH=$PATH:$HOME/CERTI/bin
export CERTI_HOST=cassis
cd $HOME/CERTI/share/federations
Then these lines, one in each terminal:
| Terminal | Command | Note |
| 1 | ./billard-init | this script starts the RTIG |
| 2 | ./billard-1 | this one starts the first billars instance |
| 3 | ./billard-2 | this on a second billard |
| 4 | ./billard-3 | this one a third billard |
or
| Terminal | Command |
| 1 | rtig |
| 2 | billard 1 on Test |
| 3 | billard 2 on Test |
| 4 | billard 3 on Test |
|
