Carbide C++: Introductory White Paper
Find more information on Eclipse, Eclipse for C/C++ development, Carbide tools, and Eclipse plug-ins.
Carbide.c++ takes advantage of the Eclipse IDE framework through plug-in modules. Nokia and Symbian Ltd. created new plug-ins to support development for Symbian OS, which replace the default set of plug-ins that created a Java IDE. These plug-ins change the standard IDE behavior as well as add new tools. Figure 2 shows Carbide.c++. Notice how the general look of Carbide matches the standard look of Eclipse as shown in Figure 1. The windows in the figure match those in Figure 1 — but with a C++ context. Many of the operational aspects of Carbide.c++ are the same as those of Eclipse.
However, Carbide.c++ has also changed many aspects of Eclipse. The look and feel is the same, but the IDE is purely C++. From menu entries to editor configurations and SDK associations, Carbide.c++ has converted a Java IDE into a Symbian OS C++ IDE. Carbide.c++ adds a new “Symbian” perspective (see the upper right-hand corner in Figure 2) that includes support for build configurations and Symbianspecificfiles such as the Application Information File (AIF) and Multiple Bitmap (MBM) files.
To achieve this, many of the Eclipse plug-in modules have been replaced or removed. The default Eclipse IDE has 101 plug-in modules defined for it; Carbide.c++ has 119. The new plug-in structure is illustrated in Figure 3. There are fundamental plug-ins that match those in the default IDE. Symbian provides core Symbian OS functional support, mostly in the form of build sequences for the various versions of the operating system software. On top of Symbian support, Nokia provides a set of plugins. These provide build support for the various SDKs — for example, the S60 platform and UIQ — and provide for new debugger and compilation behavior. Finally, there is a set of plug-ins from Freescale Semiconductor, Inc. that implement CodeWarrior® technology.