Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » Get Started Using EEROS » Deploying » Working on the Host
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 [2023/04/13 09:11] – [Examples] ursgrafgetting_started:deploy:deploy_host [2026/04/12 16:57] (current) – [Working on the Host] ursgraf
Line 9: Line 9:
 $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/eeros-project/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
Line 18: Line 19:
 $ sudo LD_LIBRARY_PATH=/home/you/work/eeros-project/install-x86/lib/ ./yourExample $ sudo LD_LIBRARY_PATH=/home/you/work/eeros-project/install-x86/lib/ ./yourExample
 </code> </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 ===== ===== 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 the examples as follows:+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> <code>
Line 29: Line 35:
 No root privileges and no other libraries are necessary. 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 If you want to run the built-in examples of EEROS
 <code> <code>
Line 34: Line 41:
 $ ./examples/logger/loggerTest $ ./examples/logger/loggerTest
 </code> </code>
-No root privileges and no other libraries are necessary. 
- 
-<code> 
-$ cd ~/eeros-project/build-x86/eeros 
-$ sudo ./examples/rtTest/rtTest 
-</code> 
-You need root privileges but no other libraries. 
- 
-<code> 
-$ cd ~/eeros-project/build-x86/eeros 
-$ sudo LD_LIBRARY_PATH=../../install-x86/lib/ ./examples/system/systemTest1 -c examples/system/SystemTest1Config.json 
-</code> 
-You need root privileges and the simulator library 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|]]. Continue with having a closer look at the examples in EEROS as described in [[getting_started:tutorials:start|]].
  
getting_started/deploy/deploy_host.1681369919.txt.gz · Last modified: by ursgraf