User Tools

Site Tools


getting_started:deploy:deploy_host

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
getting_started:deploy:deploy_host [2021/03/24 11:42] – external edit 127.0.0.1getting_started:deploy:deploy_host [2023/04/13 09:18] (current) ursgraf
Line 5: Line 5:
 </code> </code>
  
-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+To give an example: If you compiled EEROS together with the simulator wrapper library and installed them locally into ///home/you/work/eeros-project/install-x86/// you extend your path with
 <code> <code>
-$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/compiled/install-x86/lib/+$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/eeros-project/install-x86/lib/
 </code> </code>
 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. \\ 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 There is one more difficulty. If you start your application with ''sudo'', as you often have to do, you must prepend the call with
 <code> <code>
-$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} yourExample+$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./yourExample
 </code> </code>
 Alternatively, you could could use Alternatively, you could could use
 <code> <code>
-$ sudo LD_LIBRARY_PATH=/home/you/work/compiled/install-x86/lib/ yourExample+$ sudo LD_LIBRARY_PATH=/home/you/work/eeros-project/install-x86/lib/ ./yourExample
 </code> </code>
  
-Continue with the first example [[getting_started:say_hello|]] or use the examples in EEROS as described in [[getting_started:tutorials:start|]].+===== Examples ===== 
 + 
 +If you have followed the instructions given in [[getting_started:install:use_on_host|]], [[getting_started:compile_eeros_host|]] and [[getting_started:write_app:use_on_host|]] you can call the examples as follows: 
 + 
 +<code> 
 +$ cd ~/eeros-project/hello/build-x86 
 +$ ./helloworld 
 +</code> 
 +No root privileges and no other libraries are necessary. 
 + 
 +If you want to run the built-in examples of EEROS 
 +<code> 
 +$ cd ~/eeros-project/eeros/build-x86 
 +$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/eeros-project/install-x86/lib/ 
 +$ ./examples/logger/loggerTest 
 +</code> 
 +No root privileges are necessary but you have to set your library path. 
 + 
 +<code> 
 +$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./examples/rtTest/rtTest 
 +</code> 
 +You need root privileges and have to pass your library path. 
 + 
 +<code> 
 +$ cd ~/eeros-project/build-x86/eeros 
 +$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./examples/system/systemTest1 -c examples/system/SystemTest1Config.json 
 +</code> 
 +You need root privileges and the eeros and simulator libraries must be found. Further, you have to specify a hardware configuration file. 
 + 
 +Continue with having a closer look at the examples in EEROS as described in [[getting_started:tutorials:start|]].
  
getting_started/deploy/deploy_host.1616582532.txt.gz · Last modified: 2021/03/24 11:42 by 127.0.0.1