DevToolsCarbideC

[edit] Installation

Download the SDK from [Carbide Development Tools Website]
- We recommend downloading Professional Edition v1.2. You will have a 3-weeks-long evaluation license. See below on how to obtain a permanent license.
- Express Edition does not require a license and is probably good enough for most practical purposes. Version 1.2 is finally available!
Go through the HelloCarbide example described in the 'Getting Started' section of the Carbide.c++ User Guide.
- Compile the project using the Emulator Debug settings.
  - Running the executable should bring up the emulator. You should be able to find the executable called 'HelloCarbide' in the folder called 'Installed.'
- Compile the project using the Phone Release settings.
  - Double click HelloCarbide.sis which should now be in the sis folder (within the project pane). This should open Nokia PC Suite to install the executable on your S60 phone.
  - Go to your phone and navigate to the place where the application was installed (directory called 'My own') and try running it.

Hello Carbide
Deeper study of Hello Carbide
Birthdays UI Designer Tutorial
- Carbide UI designer is also described in the White Paper
- UI widgets and applications framework are described in S60 Platform Handbook
These screencasts were created with Wink

Which compiler to use? If you don't have extra compilers, GCCE for the device, "emulator debug" build for emulator.
Some routines need capabilities to run. For example, if you look at the documentation of CCamera::NewL(), you'll see that it needs a capability "UserEnvironment", which you grant at project properties (or if it's in the *.mmp file as you import it, it's copied to project properties).
- Speaking of *.mmp files, Carbide only imports from then, then ignores them, after import you need to directly modify the project properties.
Make sure the date and time on your phone is set to the same or later than the date and time on your computer. Otherwise the phone may not accept your .sis files, which will have been signed in the future from the phone's point of view.
Sometimes after emulator debugging, compiling for GCCE Phone Release might stop at 17%. Best solution may be to restart Carbide.C++ and when compiling for GCCE Phone Release pauses at 17% it should continue in a few seconds. More info found here:

 http://discussion.forum.nokia.com/forum/showthread.php?t=109074

Sometimes if certificates are not right, you might have to send to the phone with not the .sis but the .sisx file even when certificate checks are turned off in the application manager settings of the phone.