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 [2026/04/12 12:05] – [Allow Realtime Priorities] ursgrafgetting_started:deploy:deploy_host [2026/04/12 16:57] (current) – [Working on the Host] ursgraf
Line 11: Line 11:
 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 19: 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 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|]].+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|]].
  
  
Line 27: Line 27:
 ===== Examples ===== ===== Examples =====
 ===Running your Example Application=== ===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:+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>
getting_started/deploy/deploy_host.1775988321.txt.gz · Last modified: by ursgraf