Concurrent Versions System (CVS)

Carbide.c++ supports the Concurrent Versions System (CVS) for immediate version control support. Other revision systems are also supported but require the downloading of an Eclipse plug-in to add that feature to Carbide. Visit the eclipse.org or eclipse-plugins.2y.net sites to locate the plug-ins you need.

For more informaton on using CVS within Carbide, see the Workbench User Guide > Concepts > Team programming with CVS.

Software Configuration Management (SCM)

The Carbide.c++ tools are built on top of the Eclipse and CDT open source projects (eclipse.org). Carbide can use several popular software configuration management systems including:

Other revision systems are also supported but require the downloading of an Eclipse plug-in to add that capability to Carbide. Visit the eclipse-plugins.2y.net sites to locate the plug-ins you need.

diff -r 6c45b7c9cdac -r fb0e02cb252b core/com.nokia.carbide.cpp.doc.user/html/concepts/ext_build_support.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ext_build_support.htm Tue Jun 15 16:19:30 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ext_build_support.htm Wed Jun 16 11:39:35 2010 -0500 @@ -9,7 +9,7 @@

External Builds Support

The IDE will perform the following tasks on external makefiles:

The Carbide IDE performs the following tasks on external makefiles:

Build
Debug
Source Browsing
Error Lookup

The IDE can build an external makefile and debug its output. A linker plugin will enable the IDE to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.

The linker plugin will provide a preference panel named External Build that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.

Carbide can build an external makefile and debug its output. A linker plugin enables Carbide to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.

The linker plugin provides a preference panel named External Build that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.

The linker plugin is generic so that it can be used regardless of the target CPU and OS. The list of available debugger preference panels will be updated by the IDE when you select the debug platform.

The External Build Target preference panel will collect the following information:

The External Build Target preference panel collects the following information:

Build command line to be executed in the build step

@@ -38,12 +38,12 @@

If multiple build steps are performed on the same target, the output from each build step will be appended to the build output window. Each block of output will be separated by “----Build started----” and “----Done----” tags.

The build output window will allow users to navigate directly to the location of a compilation error. Double-click a line that contains an error message or press Enter when the cursor is in the line. If the IDE determines that a valid error message exists on the selected line, the source file is opened to the line on which the error occurred.

Click the right mouse button in the build output window to display a context menu.

The Copy command copies selected text to the clipboard. If no text is selected then the line that contains the cursor is copied.
The Clear All command clears the contents of output window.
The Go To Error command navigates to the error location. This is identical to double-clicking.

The Copy command will copy selected text to the clipboard. If no text is selected then the line that contains the cursor will be copied.
The Clear All command will clear contents of output window.
The Go To Error command will navigate to the error location. This is identical to double-clicking.

diff -r 6c45b7c9cdac -r fb0e02cb252b core/com.nokia.carbide.cpp.doc.user/html/concepts/images/wnd_workspace_launcher.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/wnd_workspace_launcher.png has changed diff -r 6c45b7c9cdac -r fb0e02cb252b core/com.nokia.carbide.cpp.doc.user/html/concepts/images/workbench.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/workbench.png has changed diff -r 6c45b7c9cdac -r fb0e02cb252b core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Tue Jun 15 16:19:30 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Wed Jun 16 11:39:35 2010 -0500 @@ -17,12 +17,12 @@

Install the N-Gage SDK on your PC

Place your game project inside the N-Gage SDK

In Carbide.c++, click File > Import

Select Symbian OS Bld.inf importer and navigate to your bld.inf file to import it

Select Symbian OS Bld.inf File importer and navigate to your bld.inf file to import it

Building the N-Gage project

Once the game project has been imported, use these steps to create an N-GAGE game file:

Right-click the project and choose Properties to open the Properties for project_name window
Right-click the project name and choose Properties to open the Properties for project_name window
In the Carbide.c++ > Carbide Build Configuration > SIS Builder panel, click Add.
In the SIS Properties window: