getting_started:deploy
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
getting_started:deploy [2021/03/24 11:39] – [Deploy] ursgraf | getting_started:deploy [2021/03/25 11:18] (current) – ursgraf | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | * [[.: | + | After successfully building an application it must be deployed and run either |
- | ===== Working | + | |
- | If you are running EEROS on the host machine you can omit deploying to a target | + | |
- | < | + | |
- | $ 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 | + | |
- | + | ||
- | ===== 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.1616582391.txt.gz · Last modified: 2021/03/24 11:39 by ursgraf