getting_started:deploy:deploy_manually
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
getting_started:deploy:deploy_manually [2021/03/24 17:21] – [Deploy Manually] ursgraf | getting_started:deploy:deploy_manually [2021/03/29 18:12] – ursgraf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Deploy Manually ====== | ====== Deploy Manually ====== | ||
- | If you develop EEROS itself or one of its hardware wrapper libraries, | + | |
- | + | Back to [[getting_started: | |
+ | |||
+ | 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 | ||
Next, edit '' | Next, edit '' | ||
Line 11: | Line 15: | ||
build-armhf/ | build-armhf/ | ||
</ | </ | ||
- | If you did not include the application [[https:// | + | If you did not include the application [[https:// |
- | < | + | |
- | install-armhf/ | + | |
- | install-armhf/ | + | |
- | + | ||
- | build-armhf/ | + | |
- | </ | + | |
- | 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 24: | Line 21: | ||
$ ./deploy.sh | $ ./deploy.sh | ||
</ | </ | ||
+ | |||
===== 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. |
getting_started/deploy/deploy_manually.txt · Last modified: 2021/03/29 18:14 by ursgraf