getting_started:kdevelop
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
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 ====== | ====== 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. |
+ | < | ||
+ | $ apt-get install kdevelop | ||
+ | </ | ||
- | If you have previously built your application manually or with the aid of the [[getting_started:install_and_setup_development_environment# | + | If you have previously built your application manually or with the aid of the [[https:// |
- | - Import the project by choosing the '' | + | - Import the project by choosing the '' |
- 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. // | + | - Choose the build directory of the previously built application as your build directory, e.g. // |
- 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 '' | - Click '' | ||
Line 13: | Line 16: | ||
===== 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 '' | + | - Import the project by choosing the '' |
- This will automatically open the project configuration panel. | - This will automatically open the project configuration panel. | ||
- | - Choose a meaningful build directory, e.g. // | + | - Choose a meaningful build directory, e.g. // |
- Enter an entry for the install directory, e.g. // | - Enter an entry for the install directory, e.g. // | ||
- Choose a build type. | - Choose a build type. | ||
Line 21: | Line 24: | ||
- Build | - Build | ||
- | IMPORTANT If you are using ROS in your applications make sure that you fullfill the necessary steps described in [[getting_started: | + | 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: |
getting_started/kdevelop.1616656771.txt.gz · Last modified: 2021/03/25 08:19 by ursgraf