Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Carbide.c++ Tips

From Wiki
Jump to: navigation, search
Article Metadata
Created: hamishwillee (14 Jan 2011)
Last edited: hamishwillee (16 Nov 2011)


Use the latest version

Ensure you are using the most up to date version of Carbide.c++ and that your machine meets the minimum system requirements to run Carbide. You can download the latest version of Carbide.c++ from Nokia Developer.

Build only what you need

Many new Carbide.c++ users import a monolithic project into Carbide.c++ and always build from the bld.inf file. Even though the Carbide.c++ team has made great improvements to the performance of dependency tracking, it can still be quite slow to run the makefile dependencies on large projects.

There are a couple of options which trim down the build (after your initial complete build).

  1. Open the Carbide.c++ Project Settings page (Project > Properties > Carbide.c++ > Project Settings), enable Selected Components and select just the components that you need to build.
  2. Use Build Symbian Component (CTRL+ALT+P) on the source file (CPP/RSS) you are working with. The parent MMP will be built automatically. Then follow the next tip.

Carbide.c++ Tips Figure1 .png

Turn off "Build (if required) before launching" in the Launching preference panel

This is especially useful for large projects where dependency checking can take a long time. Even though Carbide.c++ won't rebuild things that it does not need to it must still perform a dependency check on each makefile. If you ensure that your builds are up to date you can disable this check.

Carbide.c++ Tips Figure2 .png

Fix your icon makefile dependencies

This probably doesn't impact anyone working with Raptor-ized code since you should be using the new PRJ_EXTENSION for building scalable icons.

Launch epoc.exe instead of your executable when debugging

You don't always need to kill epoc.exe between debug sessions. Just close the application you are debugging, close the folder in which your application icon resides and rebuild. You can restart the application within the emulator. This doesn't work for all applications because the emulator locks some files on startup.

Select Run > Debug Configurations > Symbian OS Emulation. Set the Process to Launch field to epoc.exe. One consequence of launching epoc.exe instead of your application is that the emulator will start slowly the first time. After that you should not need to restart the emulator each time you debug your application.

Carbide.c++ tips Figure3.png

Learn the key Carbide.c++/Eclipse short cuts

Many of the features buried in the various Carbide.c++ menus can be run using keyboard shortcuts (key combinations).

Tip.pngTip: Do you have a favourite tip for using Carbide.c++? Share it with us here!

Licence icon cc-by-sa 3.0-88x31.png© 2010 Symbian Foundation Limited. This document is licensed under the Creative Commons Attribution-Share Alike 2.0 license. See for the full terms of the license.
Note that this content was originally hosted on the Symbian Foundation developer wiki.

This page was last modified on 16 November 2011, at 02:31.
27 page views in the last 30 days.