getting_started:deploy
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
getting_started:deploy [2019/10/11 16:06] – graf | getting_started:deploy [2021/03/24 11:39] – [Deploy] ursgraf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Deploy ====== | ====== Deploy ====== | ||
- | The [[https:// | ||
- | * Deploy to a Beaglebone Blue board → see [[.: | ||
+ | * [[.: | ||
+ | ===== Working on the Host ===== | ||
+ | If you are running EEROS on the host machine you can omit deploying to a target machine. However, you have to make sure that the necessary libraries can be found at runtime. We suggest not to install these libraries into your default installation directory. We recommend that you add the directory with your compiled library to your library path with | ||
+ | < | ||
+ | $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/ | ||
+ | </ | ||
+ | |||
+ | To give an example: If you compiled EEROS together with the simulator wrapper library and installed them locally into /// | ||
+ | < | ||
+ | $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/ | ||
+ | </ | ||
+ | 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 LD_LIBRARY_PATH=${LD_LIBRARY_PATH} yourExample | ||
+ | </ | ||
+ | Alternatively, | ||
+ | < | ||
+ | $ sudo LD_LIBRARY_PATH=/ | ||
+ | </ | ||
+ | |||
+ | Continue with the first example [[getting_started: | ||
+ | |||
+ | ===== Working on a Target ===== | ||
+ | If you do a cross development on a host and are using it on a target platform you have to deploy all the necessary libraries together with the application program first. | ||
+ | |||
+ | The [[https:// | ||
+ | |||
+ | * [[.: | ||
+ | * [[.: |
getting_started/deploy.txt · Last modified: 2024/06/18 11:54 by ursgraf