# Real-Time Robotics Framework

### Sidebar

getting_started:deploy

# Deploy

## Working on the Host

If you are running EEROS on the host machine you can omit deploying to a target machine. However, you have to make sure that the necessary libraries can be found at runtime. We suggest not to install these libraries into your default installation directory. We recommend that you add the directory with your compiled library to your library path with

$export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/absolute/path/to/compiled/lib/

To give an example: If you compiled EEROS together with the simulator wrapper library and installed them locally into /home/you/work/install-x86/ you extend your path with

$export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/compiled/install-x86/lib/

Please keep in mind that this path setting is valid for the current shell. As soon as you start a new shell, you have to repeat the step.
There is one more difficulty. If you start your application with sudo, as you often have to do, you must prepend the call with

$sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} yourExample

Continue with the first example Say Hello with EEROS or use the examples in EEROS as described in Tutorials.

## Working on a Target

If you do a cross development on a host and are using it on a target platform you have to deploy all the necessary libraries together with the application program first.

The EEROS scripts include a script for deployment.