Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » Get Started Using EEROS » Use KDevelop with Existing Build Configuration
getting_started:kdevelop

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:kdevelop [2021/03/25 08:20] – [Use KDevelop with Existing Build Configuration] ursgrafgetting_started:kdevelop [2021/03/25 08:30] – [No Existing Build Configuration] ursgraf
Line 4: Line 4:
  
 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: 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.   - 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.   - 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''
Line 13: Line 13:
 ===== No Existing Build Configuration ===== ===== No Existing Build Configuration =====
 If there is no existing build configuration yet, do as follows 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.   - 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//.   - Enter an entry for the install directory, e.g. //workingDirectory/install-x86//.
   - Choose a build type.   - Choose a build type.
getting_started/kdevelop.txt · Last modified: 2021/04/01 08:25 by ursgraf