User Tools

Site Tools


getting_started:kdevelop

Differences

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

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
getting_started:kdevelop [2020/02/10 11:32] – created grafgetting_started:kdevelop [2021/03/25 08:29] – [Use KDevelop with Existing Build Configuration] ursgraf
Line 1: Line 1:
 ====== Use KDevelop with Existing Build Configuration ====== ====== Use KDevelop with Existing Build Configuration ======
-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: + 
-  - Import the project by choosing the ''CMakeLists.txt'' of your project. +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. 
-  - Right click on the project and open the project configuration panel. + 
-  - Choose the build directory of the previously built application as your build directory+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/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/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.   - 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''   - Click ''Ok''
   - Build   - Build
  
-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]].+===== 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//
 +  - This will automatically open the project configuration panel. 
 +  - Choose a meaningful build directory, e.g. //workingDirectory/build-x86/eeros// or //workingDirectory/build-x86/helloWorld//
 +  - Enter an entry for the install directory, e.g. //workingDirectory/install-x86//
 +  - Choose a build type. 
 +  - Click ''Ok'' 
 +  - 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]].
getting_started/kdevelop.txt · Last modified: 2021/04/01 08:25 by ursgraf