User Tools

Site Tools


getting_started:install_and_setup_development_environment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
getting_started:install_and_setup_development_environment [2018/05/31 09:50] – external edit 127.0.0.1getting_started:install_and_setup_development_environment [2019/10/18 14:57] – [Installation and Setup] graf
Line 1: Line 1:
 ====== Installation and Setup ====== ====== Installation and Setup ======
 +For a successfull installation process you have to carefully follow the instructions below. Notably you have to
 +  - Fullfill the [[getting_started:install_and_setup_development_environment#prerequisites|Prerequisites]].
 +  - Get the sources [[getting_started:install_and_setup_development_environment#Getting_the_sources_with_a_script|]] for the right platform.
 +  - [[getting_started:compile_eeros|]]
 +  - [[getting_started:deploy|]]
 ===== Prerequisites ===== ===== Prerequisites =====
  
Line 14: Line 19:
  
 ===== Getting the Sources with a Script ===== ===== Getting the Sources with a Script =====
-Setting up the correct way of compiling EEROS can be quite cumbersome. We strongly recommend to use our scripts. Create a new and empty directory and download the scripts from +Setting up the correct way of compiling EEROS can be quite cumbersome. We strongly recommend to use our scripts. How to setup these scripts depends on your platformWhat to you want to do with EEROS? 
-<code> +  * Run examples, use with the simulator → see [[getting_started:install_and_setup_development_environment:use_on_host|]] 
-$ git clone https://github.com/eeros-project/eeros-build-scripts.git +  * Run on the host together with ROS → see [[getting_started:install_and_setup_development_environment:use_with_ros|]] 
-</code> +  * Run on the host with comedi → see [[getting_started:install_and_setup_development_environment:use_with_comedi|]] 
-  - Edit the ''config.sh.in'' file. Choose an appropriate toolchain file. The toolchain file basically determines which compiler you are going to use. If you work on the host and want to use the standard compiler you can omit this toolchain file. See [[arm_toolchain]] for an example of a toolchain file.  +  * Use it on the Beaglebone Blue board → see [[getting_started:install_and_setup_development_environment:use_on_bbb|]] 
-  - Choose a meaningful name for the build and install directory.  +  * Use it on the cb20 board with flink → see [[getting_started:install_and_setup_development_environment:use_with_cb20]] 
-  - Comment or uncomment the necessary hardware libraries. The script will fetch those left uncommented. +  * Use it with EtherCAT on x86 platform → see [[https://wiki.ntb.ch/infoportal/embedded_systems/ethercat/start]]
-  - Change the name of your application directory so that it fits your applicationIf you do not have an application to download yet, please comment these two lines out.+
  
-Now you can run the ''clone'' script  
-<code> 
-$ ./clone.sh 
-</code> 
  
 ===== Getting the Sources Manually ===== ===== Getting the Sources Manually =====
-Clone the eeros source repository:+Do this only, if you are not using the scripts mentioned above and know what you do. Clone the eeros source repository:
 <code> <code>
 $ git clone https://github.com/eeros-project/eeros-framework.git $ git clone https://github.com/eeros-project/eeros-framework.git