getting_started:compile_eeros
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:compile_eeros [2017/11/29 11:01] – [Compile Using a Script] graf | getting_started:compile_eeros [2019/10/08 16:10] – [Compile in terminal] graf | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| </ | </ | ||
| - | This will put all the executables into the build directory you have chosen and the compiled libraries together with the header files into the install directory. If you don't have an application yet, please comment the last two lines out. | + | This will put all the executables into the build directory you have chosen and the compiled libraries together with the header files into the install directory. |
| Line 41: | Line 41: | ||
| The reason for not installing EEROS globally is that you might need two or even more versions of EEROS as soon as you compile for various target architectures. For this purpose we will install various versions of EEROS into custom folders named after the target architecture by setting the CMake variable CMAKE_INSTALL_PREFIX. | The reason for not installing EEROS globally is that you might need two or even more versions of EEROS as soon as you compile for various target architectures. For this purpose we will install various versions of EEROS into custom folders named after the target architecture by setting the CMake variable CMAKE_INSTALL_PREFIX. | ||
| - | As soon as you access dedicated hardware on your system you have to install one of the [[getting_started: | + | As soon as you access dedicated hardware on your system you have to install one of the [[eeros_architecture: |