The default settings are grouped under the Defaults node in the left-hand part of the dialog box.
Find the descriptions of specific run/debug configurations in the following pages:
|Name||In this text box, specify the name of a new run/debug configuration. This field is not available for the default run/debug configurations.|
|Defaults||This node in the left-hand pane contains the default run/debug configuration settings. Select configuration to modify its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Share|| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||Select this check box to make sure that only one instance of the run/debug configuration is currently executed|
|Target||Click to choose the desired target from the list. |
Target types are marked with the following icons:
- All targets
- Custom target
|Configuration||Click to choose the desired configuration from the list|
|Program arguments||In this text box, type a list of arguments to be passed to the program in the format you would use in the command line. If necessary, click the button and type the desired arguments in the Program Parameters dialog box. |
Use the same rules as for specifying the VM options.
|Working directory||In this text box, specify the current directory to be used by the running test. This directory is the starting point for all relative input and output paths. By default, the field contains the directory where the project file resides. To specify another directory, click the Browse button select the directory in the dialog that opens. |
Click this icon to view the list of available path variables that you can use as a path to your working directory. In this case you do not need to specify any additional environment variables in the Environment variables field.
The list of path variables may vary depending on the enabled plugins.
|Environment variables||Click the Browse button to open the Environment Variables dialog box, where you can create variables and specify their values. |
Note that you can copy-paste the contents of the Environment variables field without having to open the Environment Variables dialog box.
|Generate run configurations for new CMake targets automatically||Select this check box for automatic generation of the run configurations for the new targets, following the settings of CMake Settings dialog. The run configuration is generated upon Reset CMake cache and reload a project action.|
|Confirm rerun with process termination||This check box is visible only when Defaults node is selected. |
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or folder up and down in the list. |
The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Move into new folder / Create new folder||Use this button to create a new folder. |
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list. |