Carbide.c++ Installation

Use the Carbide.c++ debugger to debug a compiled Symbian OS program in an emulator or on-device. The same process works for other emulators and target devices as well.

NOTE This example uses the emulator included with the S60 5th Edition SDK. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

NOTE This example uses the Symbian Emulator included with the Symbian^3 SDK. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

Debugging a Symbian OS program

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. A symbolics (.sym) file is also required for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.

Set a breakpoint in the MyProject program

Open the \src\MyProjectAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

Figure 1 - Breakpoint set in MyProjectAppUI::HandleCommandL routine.

Launch the Carbide debugger and S60 SDK Emulator

Start the Carbide debugger which launches the S60 SDK Emulator, installs and launches the executable. For on-device debugging, the application is installed on the target device.

The HelloCarbide application launches (Figure 2).

Figure 2 - MyProject application running on S60 Emulator

Open the \src\OortCloudAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

Figure 1 - Breakpoint set in COortCloudAppUI::HandleCommandL routine.

Launch the Carbide debugger and Symbian Emulator

Start the Carbide debugger which launches the Symbian Emulator, then installs and launches the executable. For on-device debugging, the application is installed on the target device.

The OortCloud application launches (Figure 2).

Symbian Emulator

Figure 2 - OortCloud application running on Symbian Emulator

NOTE For SDKs prior to the S60 5th Edition it may be necessary to locate the installed application and manually launch it in the emulator or on the target device.

Click the Options soft-key on the S60 Emulator to display the Options menu.
Click the Options soft-key on the Symbian Emulator to display the Options menu.
Choose the Message menu item and press the Select soft-key to send a message (Figure 3).

Figure 3 - Send Message to MyProject application

Menu selection

Figure 3 - Send Message to OortCloud application

The HandleCommandL breakpoint is hit in the program and control returns to the Carbide debugger (Figure 4). You can now set additional breakpoints, examine variables, or use the Debug view buttons to control the program.

Figure 4 - Back in the CMyProjectAppUI::HandleCommandL routine

Breakpoint hit

Figure 4 - Back in the COortCloudAppUI::HandleCommandL routine

That's it for this basic introduction to debugging with Carbide.c++.

Deploying Programs to Devices

Once you have completed the program and tested it with the emulator, it’s possible to create a new build configuration for your device, build it, then create a .sis file and deploy it to a device.

To upload a valid .sis file to the target device you need software that communicates with the target device from your PC. Every Symbian phone ships with this connectivity software, which we will refer to generically as Symbian Connect. The actual name for the software is vendor dependent, so refer to your phone’s documentation for the name.

For example, most phones from Nokia that use Symbian OS come with Nokia PC Suite, which allows you to synchronize and transfer data between your compatible phone and a compatible PC via a compatible data cable or a wireless connection.

For example, most phones from Nokia that use Symbian OS come with Ovi Suite , which allows you to synchronize and transfer data between your compatible phone and a compatible PC via a compatible data cable or a wireless connection.

Essentially, the Symbian Connect program provides a method of connecting a PC to the target device via USB, IrDA, Bluetooth, or other serial connection. Once you make a connection, you can upload your .sis file to the target device and install the program.

NOTE A simple guide is provided to show the basic steps necessary to upload a .sis file to a target device. The actual steps required by the specific Symbian Connect program that ships with the SDK you are using may differ, so always refer to that phone ’s documentation for details.

diff -r d3e4dfeca859 -r 811926adaf5e core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Thu Jun 17 13:07:08 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Thu Jun 17 13:13:02 2010 -0500 @@ -15,7 +15,7 @@

Debugging a Run-mode Project using Application TRK

Import the Bld.inf to create a project using the Import wizard

In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). When we import, we select an ARM target.

In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). For the import, we select an ARM target.

Go to the project Properties page and in the Carbide Build Configuration panel specify the PKG file in the SIS Builder tab
Build the project (Ctrl+B)
Verify that all the binaries built by the project appear in the Executables view.

Carbide.c++ Installation

System Requirements

You use the Carbide.c++ IDE in conjunction with a recognized SDK to develop Symbian software.

You use the Carbide.c++ IDE in conjunction with a recognized SDK to develop Symbian OS software.

In practice, whether you use an SDK, a developer kit (DevKit), or both depends on the edition of Carbide.c++ you have (see Table 1). Further, if you use an OS devkit, - it must be version 9.1b or higher for EKA2 with - Platform Security support.

Table 1. Support packages used for development with each Carbide.c++ Editions

An SDK or OS developer kit (DevKit) including: 9.x or higher for Platform Security	Targets: S60 5th Ed., Qt +	Targets: Symbian ^3, S60 5th Ed., Qt Debugger: Emulators, on-device debugging UI Designer: create graphical interfaces quickly using standard UI components
	Targets: S60 5th Ed., Qt +	Targets: Symbian ^3, S60 5th Ed., Qt Debugger: Emulators, on-device debugging, device debugging in ROM, kernel debugging Performance Investigator: application performance data, memory usage, power usage, button event reporting
Other Software	A Symbian OS™ SDK and Perl: +	A Symbian OS SDK and Perl: - S60 Platform SDKs (http://www.forum.nokia.com/Tools_Docs_and_Code/) - - S60 5th Edition - S60 3rd Edition, FP1 - S60 3rd Edition, MR - - - Qt - (www.trolltech.com) - - Qt SDK for S60 - - + Nokia Qt SDK + + Nokia Qt SDK + + + + + Symbian, S60 platform, and S60 device SDKs Symbian ^3 + S60 5th Editio + + Perl (www.activestate.com) (required) @@ -78,14 +75,15 @@ ActivePerl-5.6.1.635 Symbian Connect software - Software that communicates between a PC and a target device. For example, Nokia PC Suite. + Software that communicates between a PC and a target device. For example, Ovi Suite. +
Disk Space	800 MB for Carbide.c++ - Up to 2.0 GB for each S60 SDK installation + Up to 2.0 GB for each SDK installation

NOTE Always run the Help > Check for Updates wizard and install all updates before attempting to install new software. This can prevent the occurrence of any dependency errors.

Select Help > Install New Software... to display the Available Software pane of the Install dialog. -
+

Figure 1 - Install dialog - Available Software pane
1. Select an update site from the Work with drop down, or click Add... to enter a new site URL.
2. Click Next
In the Install Details pane select the specific items to install from those displayed, then click Next. -
-
Figure 2 - Install dialog - Install Details pane
-
Review the items to install in the second Install Details pane, then click Next. -
-
Figure 3 - Install dialog - second Install Details pane
+
+
Figure 2 - Install dialog - Install Details pane
Accept the license terms, then click Finish. -
-
Figure 4 - Install dialog -Review Licenses pane
+
+
Figure 3 - Install dialog -Review Licenses pane

Debugging a Symbian OS Program

Debugging a Symbian OS program

Deploying Programs to Devices

Debugging a Run-mode Project using Application TRK

System Requirements

Table 1. Support packages used for development with each Carbide.c++ Editions