To run or debug a project you need a launch configuration. A project must have at least one launch configuration, and can have as many as necessary. When run on an emulator project the wizard simply creates an emulator launch configuration and launches the emulator. When running a device project for the first time the New Launch Configuration Wizard seeks additional information required to create the launch configuration, then downloads the executable to the device and launches it. Once the emulator or device are loaded with the executable, the debug session can commence.
There are two methods for setting up a launch configuration, including:
NOTE Carbide.c++ only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide.c++ launches that instead.
or
Carbide.c++ creates a default launch configuration for the project and begins running or debugging the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration:
NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items.
In the event that the default launch configuration settings need to be changed, it is possible to edit them in the Debug window, or create a new launch configuration for the project that deviates from the default settings.
The appropriate Run or Debug launch configuration window appears (Figure 1).
Figure 1 - Initial blank Debug launch configuration window
A new configuration appears in the Configuration list under the appropriate section using the project name and target to create the configuration name.
NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.
Figure 2 - New launch configuration with name and settings filled in (emulator)
Modify or fill in the following fields in the Main tab so the IDE can setup the configuration properly each time. Typically when creating a new executable from a project that has successfully linked, the fields will be auto-populated and do not need to be modified. The important fields here are:
To debug something outside of the workspace, be sure to import the binary into the Executables view.
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.