Differences

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

--- getting_started:kdevelop [2021/03/25 08:19] – ursgraf
+++ getting_started:kdevelop [2021/04/01 08:25] (current) – [No Existing Build Configuration] ursgraf
@@ Line 1: / Line 1: @@
 ====== Use KDevelop with Existing Build Configuration ======
-Using an integrated development environment for developing EEROS applications is highly recommended. You have all the features such as source code lookup, code completion or automatic compiling.
+Using an integrated development environment for developing EEROS applications is highly recommended. You have all the features such as source code lookup, code completion or automatic compiling. We recommend to use an integrated development environment such as [[https://www.kdevelop.org/]] or [[https://code.visualstudio.com/]]. Get the program with e.g.
+<code>
+$ apt-get install kdevelop
+</code>
-If you have previously built your application manually or with the aid of the [[getting_started:install_and_setup_development_environment#Getting_the_Sources_with_a_Script|EEROS build scripts]], you can import the configuration into KDevelop as follows:
+If you have previously built your application manually or with the aid of the [[https://github.com/eeros-project/eeros-build-scripts.git|EEROS scripts]], you can import the configuration into KDevelop as follows:
-  - Import the project by choosing the ''CMakeLists.txt'' of your project, eg. //workingDirectory/eeros/CMakeLists.txt// or //workingDirectory/helloWorld/CMakeLists.txt//.
+  - Import the project by choosing the ''CMakeLists.txt'' of your project, eg. //workingDirectory/hello/CMakeLists.txt// or //workingDirectory/simple-motor-control/CMakeLists.txt//.
   - This will automatically open the project configuration panel.
-  - Choose the build directory of the previously built application as your build directory, e.g. //workingDirectory/build-x86/eeros// or //workingDirectory/build-x86/helloWorld//
+  - Choose the build directory of the previously built application as your build directory, e.g. //workingDirectory/build-x86/hello// or //workingDirectory/build-x86/simple-motor-control// {{ :getting_started:kdev-build-config.png?600 |}}
   - Leave the entries for install directory, build type, and extra arguments empty. These settings will be fetched from the existing CMake configuration in your build directory.
   - Click ''Ok''
@@ Line 13: / Line 16: @@
 ===== No Existing Build Configuration =====
 If there is no existing build configuration yet, do as follows
-  - Import the project by choosing the ''CMakeLists.txt'' of your project, eg. //workingDirectory/eeros/CMakeLists.txt// or //workingDirectory/helloWorld/CMakeLists.txt//.
+  - Import the project by choosing the ''CMakeLists.txt'' of your project, eg. //workingDirectory/hello/CMakeLists.txt// or //workingDirectory/simple-motor-control/CMakeLists.txt//.
   - This will automatically open the project configuration panel.
-  - Choose a meaningful build directory, e.g. //workingDirectory/build-x86/eeros// or //workingDirectory/build-x86/helloWorld//.
+  - Choose a meaningful build directory, e.g. //workingDirectory/build-x86/hello// or //workingDirectory/build-x86/simple-motor-control//.
   - Enter an entry for the install directory, e.g. //workingDirectory/install-x86//.
   - Choose a build type.
@@ Line 21: / Line 24: @@
   - Build
-IMPORTANT If you are using ROS in your applications make sure that you fullfill the necessary steps described in [[getting_started:ros#Preparations_and_Building|ROS: Preparations and Building]].
+IMPORTANT If you are using an SDK for a given target or ROS in your applications, make sure that you source the SDK and fullfill the necessary steps described in [[getting_started:ros#Preparations_and_Building|ROS: Preparations and Building]] before starting the IDE.