User Tools

Site Tools


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 revisionBoth sides next revision
getting_started:kdevelop [2021/03/25 08:29] – [Use KDevelop with Existing Build Configuration] ursgrafgetting_started:kdevelop [2021/03/25 08:29] – [Use KDevelop with Existing Build Configuration] ursgraf
Line 6: Line 6:
   - Import the project by choosing the ''CMakeLists.txt'' of your project, eg. //workingDirectory/hello/CMakeLists.txt// or //workingDirectory/simple-motor-control/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/hello// or //workingDirectory/build-x86/simple-motor-control// {{:getting_started:kdev-build-config.png?400|}}+  - 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''
getting_started/kdevelop.txt · Last modified: 2021/04/01 08:25 by ursgraf