Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » Get Started Using EEROS » Deploying » Deploy Manually
getting_started:deploy:deploy_manually

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_manually [2021/03/25 19:34] – ursgrafgetting_started:deploy:deploy_manually [2021/03/29 18:14] (current) – [Set Library Links] ursgraf
Line 3: Line 3:
 Back to [[getting_started:compile_eeros_man|]]. Back to [[getting_started:compile_eeros_man|]].
  
-If you develop EEROS itself or one of its hardware wrapper libraries, your target image does not yet include these libraries of it has an older version which you may want to replace. How to proceed? +If you work on the host, there is no need to deploy anything.  
- + 
 +If you develop EEROS itself or one of its hardware wrapper libraries another target platform, the target image does not yet include these libraries or it may has an older version which you may want to replace. How to proceed?
  
 Next, edit ''deploy.txt'' in your project directory and enter all the programs and libraries you have to transfer. Next, edit ''deploy.txt'' in your project directory and enter all the programs and libraries you have to transfer.
Line 14: Line 15:
 build-armhf/simple-motor-control/simpleMotorControl build-armhf/simple-motor-control/simpleMotorControl
 </code> </code>
-If you did not include the application [[https://github.com/eeros-project/simple-motor-control.git]] you have to alter the last two lines and set the entries according to your needs. E.g. if you wrote your own [[getting_started:say_hello|]] the file would look like +If you did not include the application [[https://github.com/eeros-project/simple-motor-control.git]] you have to alter the last two lines and set the entries according to your needs. 
-<code> +
-install-armhf/lib/libeeros.so.1.2.0.0 +
-install-armhf/lib/libbbblueeeros.so.1.2.0.0 +
- +
-build-armhf/helloworld +
-</code> +
-Obviously, this application does not make use of a hardware configuration file.+
  
 Finally, load them onto the target with Finally, load them onto the target with
Line 27: Line 21:
 $ ./deploy.sh $ ./deploy.sh
 </code> </code>
 +
 ===== Set Library Links ===== ===== Set Library Links =====
-The system must find the eeros and hardware wrapper libraries to dynamically load them. The following symbolic links must be created once.+The system must find the eeros and hardware wrapper libraries to dynamically load them. The following symbolic links must be created once. The example is given for a Beaglebone Blue board.
  
 <code> <code>
-debian@beaglebone:$ cd /usr/lib/ +ost@bblue:$ cd /usr/lib/ 
-debian@beaglebone:$ sudo ln -s /opt/eeros/lib/libbbblueeeros.so.1.2.0.0 libbbblueeeros.so.1.2.0.0 +ost@bblue:$ sudo ln -s /opt/eeros/lib/libbbblueeeros.so.1.2.0.0 libbbblueeeros.so.1.2.0.0 
-debian@beaglebone:$ sudo ln -s libbbblueeeros.so.1.2.0.0 libbbblueeeros.so +ost@bblue:$ sudo ln -s libbbblueeeros.so.1.2.0.0 libbbblueeeros.so 
-debian@beaglebone:$ sudo ln -s /opt/eeros/lib/libeeros.so.1.2.0.0 libeeros.so.1.2.0.0 +ost@bblue:$ sudo ln -s /opt/eeros/lib/libeeros.so.1.2.0.0 libeeros.so.1.2.0.0 
-debian@beaglebone:$ sudo ln -s libeeros.so.1.2.0.0 libeeros.so+ost@bblue:$ sudo ln -s libeeros.so.1.2.0.0 libeeros.so
 </code> </code>
 IMPORTANT Make sure the version information (....so.1.2.0.0) is not outdated! If you use newer versions of the libraries as given in ''deploy.txt'' you must adapt the links accordingly. IMPORTANT Make sure the version information (....so.1.2.0.0) is not outdated! If you use newer versions of the libraries as given in ''deploy.txt'' you must adapt the links accordingly.
  
getting_started/deploy/deploy_manually.1616697284.txt.gz · Last modified: 2021/03/25 19:34 by ursgraf