getting_started:compile_eeros_man
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
getting_started:compile_eeros_man [2021/02/12 17:09] – external edit 127.0.0.1 | getting_started:compile_eeros_man [2021/10/24 11:46] (current) – [Compile Additional Libraries] ursgraf | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Compile ====== | + | ====== Compile |
+ | Back to [[getting_started: | ||
- | ===== Compile | + | Compile and install |
- | As mentioned in [[getting_started: | + | |
< | < | ||
- | install_dir=" | + | $ mkdir build-x86 |
- | build_dir=" | + | $ cd build-x86 |
+ | $ mkdir eeros | ||
+ | $ cd eeros | ||
+ | $ cmake -DCMAKE_INSTALL_PREFIX=../ | ||
+ | $ make | ||
+ | $ make install | ||
</ | </ | ||
+ | If your target architecture is different from the host platform we suggest to use a SDK. If you don't use a SDK, you have to specify a toolchain file with as given in [[getting_started: | ||
- | + | Per default, debug information will be included in the code. For maximum efficiency | |
- | If you use ROS you have to make sure to take necessary steps as given in [[getting_started:ros# | + | |
- | After this you proceed with | + | |
< | < | ||
- | $ ./make.sh | + | $ cmake -DCMAKE_INSTALL_PREFIX=../../ |
</ | </ | ||
- | 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. Please keep in mind that build and install directory are both defined in '' | ||
- | Continue with [[getting_started: | + | ===== Compile Hardware Wrapper Libraries ===== |
+ | As soon as you access dedicated hardware on your system you have to install one of the [[eeros_architecture: | ||
+ | < | ||
+ | $ git clone https:// | ||
+ | </ | ||
- | + | Build and install | |
- | ===== Compile Manually in Terminal ===== | + | |
- | Compile | + | |
< | < | ||
- | $ cd path/ | + | $ cd build-x86 |
- | $ mkdir build-eeros-x86-64 | + | $ mkdir sim-eeros |
- | $ cd build-eeros-x86-64 | + | $ cd sim-eeros |
- | $ cmake -DCMAKE_INSTALL_PREFIX=/ | + | $ cmake -DCMAKE_INSTALL_PREFIX=../../ |
$ make | $ make | ||
$ make install | $ make install | ||
- | </ | ||
- | If your target architectur is different from the host platform you have to use a //tool chain file//. For more information see above [[getting_started: | ||
- | Per default, debug information will be included in the code. For maximum efficiency make sure to change the 4th line to: | ||
- | < | ||
- | $ cmake -DCMAKE_INSTALL_PREFIX=/ | ||
</ | </ | ||
+ | Continue with [[getting_started: | ||
- | We recommend to not install EEROS globally | + | ===== Compile Additional Libraries ===== |
- | < | + | |
- | $ make install | + | Some blocks of the control system use further libraries such as CANOpen, LibUSB, MODBUS and so on. You have to fetch, |
- | </ | + | |
- | The reason for not installing | + | |
< | < | ||
- | $ cmake -DCMAKE_INSTALL_PREFIX=/ | + | $ cmake -DCMAKE_INSTALL_PREFIX=../../ |
</ | </ | ||
+ | when using the CANOpen library. These will also compile the EEROS examples which demonstrate the use of CAN. | ||
- | As soon as you access dedicated hardware on your system you have to install one of the [[eeros_architecture: |
getting_started/compile_eeros_man.1613146164.txt.gz · Last modified: 2021/02/12 17:09 by 127.0.0.1