Back to Compile Manually.
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?
deploy.txt in your project directory and enter all the programs and libraries you have to transfer.
install-armhf/lib/libeeros.so.22.214.171.124 install-armhf/lib/libbbblueeeros.so.126.96.36.199 build-armhf/simple-motor-control/HwConfigBBBlue.json build-armhf/simple-motor-control/simpleMotorControl
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.
Finally, load them onto the target with
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 example is given for a Beaglebone Blue board.
ost@bblue:$ cd /usr/lib/ ost@bblue:$ sudo ln -s /opt/eeros/lib/libbbblueeeros.so.188.8.131.52 libbbblueeeros.so.184.108.40.206 ost@bblue:$ sudo ln -s libbbblueeeros.so.220.127.116.11 libbbblueeeros.so ost@bblue:$ sudo ln -s /opt/eeros/lib/libeeros.so.18.104.22.168 libeeros.so.22.214.171.124 ost@bblue:$ sudo ln -s libeeros.so.126.96.36.199 libeeros.so
Make sure the version information (….so.188.8.131.52) is not outdated! If you use newer versions of the libraries as given in
deploy.txt you must adapt the links accordingly.