Translations:KDevelop5/Manual/Running programs/5/en: Difference between revisions

From KDE UserBase Wiki
(Importing a new version from external source)
 
(Importing a new version from external source)
Line 1: Line 1:
To set this up go to menu item <menuchoice>Run -> Configure launches</menuchoice>, highlight the project you want to add a launch for, and click on the {{Plus}} button. Then enter the name of the executable, and the path where you want to run the program. If running the executable depends on building the executable and/or other libraries first, then you may want to add them to the list at the bottom: select <menuchoice>Build</menuchoice> from the dropdown menu, then hit the {{Icon|folder}} symbol to the right of the textbox and select whatever target you want to have built. In the example above, I have selected the target <menuchoice>all</menuchoice> from project '''''1.deal.II''''' and '''''step-32''''' from project '''''1.step-32''''' to make sure both the base library and the application program have been compiled and are up to date before the program is actually executed. While you're there, you may as well also configure a debug launch by clicking on the <menuchoice>Debug</menuchoice> symbol and adding the name of 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.
To set this up go to menu item <menuchoice>Run -> Configure launches</menuchoice>, highlight the project you want to add a launch for, and click on the {{Plus}} button. Then enter the name and location of the executable, and the path where you want to run the program.  Any required command line arguments if any, can be specified in the <menuchoice>Arguments:</menuchoice> edit box. If running the executable depends on building the executable and/or other libraries first, then you may want to add them to the list at the bottom: select <menuchoice>Build</menuchoice> from the dropdown <menuchoice>Action:</menuchoice> menu, then hit the {{Icon|folder}} symbol to the right of the textbox and select whatever target you want to have built. While you're there, you may as well also configure a debug launch by clicking on the <menuchoice>Debug</menuchoice> symbol and adding the name of 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.

Revision as of 09:59, 6 September 2020

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (KDevelop5/Manual/Running programs)
*  Select <menuchoice>Run -> Configure launches</menuchoice> from the menubar.
*  Highlight the project you want to add a launch for and click on the {{Plus}}/<menuchoice>Add</menuchoice> 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 <menuchoice>Arguments:</menuchoice> edit box.

To set this up go to menu item Run -> Configure launches, highlight the project you want to add a launch for, and click on the button. Then enter the name and location of the executable, and the path where you want to run the program. Any required command line arguments if any, can be specified in the Arguments: edit box. If running the executable depends on building the executable and/or other libraries first, then you may want to add them to the list at the bottom: select Build from the dropdown Action: menu, then hit the symbol to the right of the textbox and select whatever target you want to have built. While you're there, you may as well also configure a debug launch by clicking on the Debug symbol and adding the name of 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.