S60 Open to new features

When we first released Carbide we quickly learned from users that the concept of a "launch configuration" was pretty obscure to most folks. A UI evaluation team even came in and looked at us really weird when we brought the concept up. Carbide inherited the concept from Eclipse and we been refining it ever since. Basically, its a set of external data not required by the program but essential in setting the conditions so Carbide can launch and debug it. It contains information like which emulator to launch, which COM port ID to use, and other information.

In Carbide 1.2 we introduced the New Launch Configuration Wizard for on-device TRK debugging, JTAG debugging, and attaching to processes. In Carbide 1.3.1 we've gone back, reevaluated the entire launch configuration wizard process and refined it a bit to make it more useful to all users. Basically, unless your program has special customization requirements, you really should never have to go to the Debug window again.

Here's how it works.

Once you've imported or created a new program from a template, select the build configuration to debug (emulator, GCCE, RVCT, etc.) using the Build icon () to build it, then click the Debug icon () in the toolbar. The New Launch Configuration Wizard determines if a launch configuration exists for the chosen build. If one already exists, that launch configuration starts. If this is the first time launching the project then New Launch Configuration Wizard kicks in to gather any additional info it needs to launch the program.

Figure 1. Launch Types page

Emulator projects
For emulator projects, the wizard gathers all the info it needs from the project itself, creates a Symbian OS Emulator launch configuration using that data and names it for you. Finally, it actually launches the program into the emulator so you can begin debugging. From your perspective, once you click Debug the program launches the emulator, the Debug perspective appears in Carbide and you are off to the debugging races.

On-device projects
For on-device targets using Application TRK, System TRK, Trace32, Sophia, and attaching to processes, the wizard needs additional information in order to launch and debug the project.

Once you click Debug and the New Launch Configuration Wizard starts the first page covers the various Launch Types (Figure 1). The launch types are listed in the order most often used. Application TRK leads the pack with Attach to Process trailing. Select a Launch Type most appropriate for the project's build configuration and click Next.

Figure 2. Executable Selection page

On the Executable Selection page you select the Executable to Launch if more than one EXE exists, otherwise your EXE choice is made for you, then verify that its the correct EXE by examining the Location text box. Use the new Specify device or emulator path of executable to launch field to enter in a specific target destination for the EXE. Some common destinations include c:\sys\bin for RAM, z:\sys\bin for ROM, and e:\sys\bin for memory cards. Once you're happy with the EXE selection and destination, click Next.

Figure 3. TRK Connection Settings page

The TRK Connection Settings page follows where you choose the Serial Port that Carbide should use to communicate with the target device. If you used the On-Device Setup dialog that is included with Carbide 1.3.1 then you'll know immediately which one to choose. Otherwise, as a good rule of thumb, opt for choosing ports that have names associated with them as this usually indicates a known connection. When done, click Next.

Figure 4. TRK SIS Selection page

The TRK SIS Selection page enables you to choose which SIS file is uploaded to the target device. If multiple SIS files are available, simply choose from the dropdown list. If none are available, click the Modify SIS builder settings for build configuration link to open the Properties for Project > Carbide.c++ > Carbide Build Configuration > SIS Builder page where you can add, edit, or remove the SIS files associated with the project.

Figure 5. New Launch Configuration page

The final wizard page is the New Launch Configuration page where we now actually provide a summary of the choices made on all previous pages. Now you really can review the list and see if anything needs changes. If so, click the Back and revise. If you're satisfied with the settings you've chose, click Finish to create the new launch configuration and then you're off to debug your project.

Customization
The last option to speak of on this page is the Open launch configuration for additional customization... checkbox. If you enable this option, clicking Finish will create the new launch configuration and then open it in the Debug dialog where you can set additional options. Unless you are doing something really unique selecting this for your initial debug excursion is not recommended. Carbide uses the info you just provided along with info gathered from the project to create a functioning launch configuration. Setting additional options at this time is not a good idea. However, once you've confirmed that the new launch configuration works, feel free to go back and change a few things in order to debug your project. You will probably find that you never need to open the Debug dialog again.

If you somehow manage to enter data that makes that launch configuration no longer work, just delete it and click the Debug icon again to create a new fresh launch configuration.