## Carbide.c++ Release Notes 3.0.0

The Carbide.c++ is a comprehensive development tool suite for Symbian OS that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE.

This is a collection of important information concerning last-minute changes and other topics that deserve special attention. Please read these notes carefully before using the Carbide tools so you understand the current limitations and workarounds for known issues.

- What's new
- User notes
- K nown issues
- Bug Fixes
- Technical support

Once you have read the release notes, we recommend you follow the HelloWorld tutorial for a quick introduction to Carbide.c++.

WARNING: Updating the CDT feature in Carbide.c++/Eclipse will wipe out our changes making the tools unusable!

### What's New in 3.0.0

The following features for Symbian development are provided within Carbide.c++:

- Eclipse 3.6 — The Eclipse 3.6 project (Helios) provides the foundation, or integration platform, on which Carbide.c++ is built. See What's New in 3.6 for more information.
- CDT 7.0 — The final version of CDT is included as part of the Helios release. See the CDT 7.0 News and Noteworthy page for more information.
- Eclipse Debugger for C/C++ — Carbide now uses the Eclipse Debugger for C/C++ (EDC) as its default debugger. EDC provided an entirely new Debug view with all of the standard debug features like variables, breakpoints, watchpoints, disassembly, and all the other views required to run a debugging session. In addition, EDC provides the framework to add new debug features like snapshots.
- Customized Carbide environment — Carbide introduces Plugin Discovery Sites where you can search for and download Carbide plugins to customize your Carbide environment. Think of it as an app store for plugins. It uses the Eclipse P2 feature to provide a common framework for finding, installing, updating, and removing plugins from the Carbide environment.
- Improved UI — Carbide's UI has been streamlined and minimized to a core set of functionality, mainly that of creating Symbian projects, building and debugging them. Context menus have been reworked to show a minimum set of options. If your favorite option is missing, you can use the Capability preference panel or the Customize Perspective dialog to add favorite commands back onto the context menus.
- Performance improvements — We continue to address known performance issues as they reveal themselves. This release provides improvements for:
  - Stack frames — in the Debug view stack frames were displayed once the symbol tables were completely read. For large symbol files this sometimes slowed down the display and hence the ability to continue debugging. Now the Debug view will show a subset of stack frames after a set time and update the remainder once it has finished scanning the symbol file.
  - Executables view — eliminated several use cases that forced the Executables list to update to frequently.
  - Large symbol tables supported — The Carbide symbol reader has been rewritten to provide faster access to symbols and to handle very large symbol files (larger than 10GB).

#### 2.6.0

- GCCE 4.0 supported — required for future SBSv2 releases.
- Symbian^3 supported — new templates and improvements required for the public Symbian^3 SDK.
- Known Issues in v2.6.0:
  - GCCE4 support requires using a SBSv2 build alias (-c parameter) of armv5_udeb_gcce or armv5_urel_gcce. As of this writing, these aliases were not available in the SDK or SBSv2, but will appear in some future version. Carbide versions prior to 2.6 do not support GCCE4.
  - Users should consult the SDK documentation for GCCE and SBSv2 issues and installation requirements.
  - TRK: If you install the TRK app onto your phone's flash memory (Mass Storage) a Remote Connection may not find the TRK-service even though TRK is already connected to your PC. Workaround: Uninstall TRK then reinstall it onto your PHONE memory (C-drive). The TRK service should now be "Available".

#### 2.5.0

- Plug-and-Play (PnP) On-device Debugging supported — debugging a target device just got easier. Using a USB cable, connect the PC to the target device, then launch Carbide.c++. Carbide locates the connected device and creates a remote connection setup to communicate with it. Build the program and launch it on the device to start the debugging session. Refer to Known PnP Issues for details if you experience problems.
- PnP Phone Launch Wizard - If the project does not already have a launch configuration, the PnP Launch Wizard makes it easy to create one for phones. In addition the new Configure Launch Configuration dialog provides a quick summary of the remote connection for easy review and modification.
- Carbide automatically detects TRK on target phones and devices - Carbide now detects the presence of either Application or System TRK on a connected device when TRK 3.2.6 or later are installed. Earlier TRK versions do not support this recognition feature.
- TRK improvements - TRK continues to evolve and now includes these improvements:
  - Both Application and System TRK v3.2.6 support PnP debugging. Update and install using the Help > On Device Connections > Install Remote Agents pane in the New Connection dialog.
  - VERSION3 command now supported
- RVCT 4.0 (ARMv5) builds and some limited debugging is supported
- Symbian ^3 SDK now supported

### Known issues

Workarounds for known issues:

- Qt issues — If Qt does not seem to be working as expected, be sure to run the \configuration\qt\register_plugins.bat file to properly register the Qt plugins. This is especially important if you installed Carbide using a zip file and not an installer.

### Technical support

The following support services are available:

- Visit the Symbian Foundation for Carbide.c++ and Symbian development information