KDevelop5/Manual/Running programs: Difference between revisions
m made it in a steps form for a more clear way to launch a configuration |
Marked this version for translation |
||
Line 22: | Line 22: | ||
Any required command line arguments can be specified in the <menuchoice>Arguments:</menuchoice> edit box. | Any required command line arguments can be specified in the <menuchoice>Arguments:</menuchoice> edit box. | ||
<!--T:17--> | |||
[[File:KDevelop-arguments-config.png.png|800px|thumb|center]] | [[File:KDevelop-arguments-config.png.png|800px|thumb|center]] | ||
<!--T:18--> | |||
If you need to build the executable or add libraries before running it,add the dependencies tab at the bottom of the page, | If you need to build the executable or add libraries before running it,add the dependencies tab at the bottom of the page, | ||
* select <menuchoice>Build</menuchoice> from the dropdown <menuchoice>Action:</menuchoice> menu. | * select <menuchoice>Build</menuchoice> from the dropdown <menuchoice>Action:</menuchoice> menu. | ||
Line 29: | Line 31: | ||
* Click Ok. | * Click Ok. | ||
<!--T:19--> | |||
To configure a debug launch: | To configure a debug launch: | ||
* Select on the <menuchoice>Debug</menuchoice> symbol under the selected launch configuration on the left tab. | * Select on the <menuchoice>Debug</menuchoice> symbol under the selected launch configuration on the left tab. | ||
* add the path to the debugger program. | * add the path to the debugger program. | ||
<!--T:20--> | |||
if this is the system's default debugger (e.g. '''gdb''' on Linux), then you don't need to do this step. | if this is the system's default debugger (e.g. '''gdb''' on Linux), then you don't need to do this step. | ||
Latest revision as of 04:48, 27 August 2020
Running programs in KDevelop
Once you have built a program, you will want to run it. To do this, need to configure Launches for your project. A Launch consists of the name of an executable, a set of command line parameters, and an execution environment (such as "run this program in an external terminal", or "run this program in the debugger").
Setting up launches in KDevelop
![](/images.userbase/thumb/0/0e/Kdevelop-nano-launch-config.png/500px-Kdevelop-nano-launch-config.png)
- Select from the menubar.
- Highlight the project you want to add a launch for and click on the
/ button.
- From the drop down menu shown, select the name of the launch configuration.
- Enter the name you want to call the launch configuration (you can edit it later by double clicking it ).
- In the executable tab, choose the project target or the path where you want to run the program.
Any required command line arguments can be specified in the
edit box.![](/images.userbase/thumb/1/16/KDevelop-arguments-config.png.png/800px-KDevelop-arguments-config.png.png)
If you need to build the executable or add libraries before running it,add the dependencies tab at the bottom of the page,
- select from the dropdown menu.
- Select the
symbol to the right of the textbox and select whatever target you want to have built.
- Click Ok.
To configure a debug launch:
- Select on the symbol under the selected launch configuration on the left tab.
- add the path to the debugger program.
if this is the system's default debugger (e.g. gdb on Linux), then you don't need to do this step.
![](/images.userbase/thumb/1/1e/Kdevelop-after-nano-run.png/650px-Kdevelop-after-nano-run.png)
To run the program:
- From the menu bar, select Shift + F9. or use the shortcut
Your program should now run in an external terminal window of KDevelop. The picture above shows the result: The new
tool subwindow at the bottom shows the output of the program that is being run, in this case the nano text editing program.
Some useful keyboard shortcuts
Running a program | |
---|---|
F8 | Build (call make) |
Shift + F9 | Run |
F9 | Run program in the debugger; you may want to set breakpoints beforehand, for example by right-clicking with the mouse on a particular line in the source code |