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

Both sides previous revisionPrevious revision
Next revision
Previous revision
getting_started:deploy:deploy_host [2021/03/25 08:05] ursgrafgetting_started:deploy:deploy_host [2026/04/12 16:57] (current) – [Working on the Host] ursgraf
Line 7: Line 7:
 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 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'', 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> 
 +Keep in mind that it is preferable to not run your EEROS application with ''sudo''. This can lead to problems when working together with ROS. ''sudo'' is necessary when the executor tries to alter scheduling parameters or when certain device file such as ''/dev/mouse'' or ''/dev/ttyUSB0'' must be accessed. Follow directions given in [[getting_started:tutorials:rttest|]] or [[getting_started:tutorials:inputdev1|]] to avoid running your program with ''sudo''
 + 
 +Keep in mind that if you have built EEROS with ROS support, you have to source the setup script before running any EEROS application as given in [[getting_started:ros_prep|]]. 
 + 
 + 
 + 
 +===== Examples ===== 
 +===Running your Example Application=== 
 +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 your EEROS application as follows: 
 + 
 +<code> 
 +$ cd ~/eeros-project/hello/build-x86 
 +$ ./helloworld 
 +</code> 
 +No root privileges and no other libraries are necessary. 
 + 
 +===Running the Built-in Examples=== 
 +If you want to run the built-in examples of EEROS 
 +<code> 
 +$ cd ~/eeros-project/eeros/build-x86 
 +$ ./examples/logger/loggerTest
 </code> </code>
  
-Continue with the first example [[getting_started:say_hello|]] or use the examples in EEROS as described in [[getting_started:tutorials:start|]].+Continue with having a closer look at the examples in EEROS as described in [[getting_started:tutorials:start|]].
  
getting_started/deploy/deploy_host.1616655909.txt.gz · Last modified: by ursgraf