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/06/22 08:38] – [Compile Using a Script] graf | getting_started:compile_eeros [2019/04/25 11:39] – [Compile Using a Script] graf | ||
---|---|---|---|
Line 4: | Line 4: | ||
===== Compile Using a Script ===== | ===== Compile Using a Script ===== | ||
- | As mentioned in [[getting_started: | + | As mentioned in [[getting_started: |
- | ===== Compile with KDevelop ===== | + | |
- | Start KDevelop and fetch the EEROS source from Github by selecting **Project** | + | < |
+ | $ ./make.sh | ||
+ | </code> | ||
- | {{: | + | 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. |
- | Enter the **destination** and the **[[https:// | ||
- | {{: | ||
- | |||
- | After the source has been fetched click **Next**: | ||
- | |||
- | {{: | ||
- | |||
- | Select the **CMakeLists.txt** file and click **Next**: | ||
- | |||
- | {{: | ||
- | |||
- | Enter the name of the project in KDevelop and click **Finish**: | ||
- | |||
- | {{: | ||
- | |||
- | Enter the location where EEROS should be build into the field **Build Directory**. It is recommended that you name this folder // | ||
- | |||
- | Enter the location where EEROS should be installed to into the filed **Installation Prefix**. If you want to install EEROS globally on the current system then leave this field empty. It is recommended that you specify a location and that you name it // | ||
- | |||
- | Do not forget to choose the build type. Per default it will be '' | ||
- | |||
- | Enter any additional CMake arguments into the field **Extra Arguments**. If you want to cross-compile EEROS enter the path to the toolchain file (e.g. -DCMAKE_TOOLCHAIN_FILE=path/ | ||
- | |||
- | Click **OK** to configure CMake. Before we build EEROS, a stable version should be checked out: | ||
- | |||
- | {{: | ||
- | |||
- | Right-click the EEROS Project and select **Git** > **Branches**: | ||
- | |||
- | {{: | ||
- | |||
- | Select the stable branch you like and click **Checkout**. Stable branches have the format STABLEVERSION.x (e.g. 0.4.x, 0.5.x, 1.0.x, ...). | ||
- | |||
- | {{: | ||
- | |||
- | Build EEROS by clicking on the **Build** button. | ||
- | |||
- | {{: | ||
- | |||
- | Install EEROS by right-clicking on the project and selecting **Install**. This last step will install the header files into the directory **include** and the compiled library into the directory **lib**. The directory **lib** will also contain some necessary cmake files to compile EEROS applications. | ||
===== Compile in terminal ===== | ===== Compile in terminal ===== | ||
- | |||
- | Clone the EEROS source repository: | ||
- | < | ||
- | $ cd path/ | ||
- | $ git clone https:// | ||
- | </ | ||
- | |||
- | Checkout a stable version of EEROS: | ||
- | < | ||
- | $ cd eeros-framework | ||
- | $ git checkout v0.5 | ||
- | </ | ||
- | |||
- | Tags in the format vX.Y are stable releases. To show all tags execute the following command: | ||
- | < | ||
- | $ git tag | ||
- | </ | ||
- | |||
Compile and install EEROS to a custom folder: | Compile and install EEROS to a custom folder: | ||
< | < | ||
Line 87: | Line 30: | ||
</ | </ | ||
+ | |||
+ | We recommend to not install EEROS globally on your system. However, if you want to install EEROS globally you have to execute the following commands: | ||
+ | < | ||
+ | $ mkdir build | ||
+ | $ cd build | ||
+ | $ cmake .. | ||
+ | $ make | ||
+ | # make install | ||
+ | </ | ||
+ | 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: |