diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/build_configurations.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_configurations.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_configurations.htm Tue Apr 13 15:55:45 2010 -0500 @@ -15,7 +15,7 @@
  • a build configuration - a project level configuration that includes an SDK and any related files required to compile and build the project
  • Build configurations are defined when the project is created. A project can have any number of build configurations and more can be added as necessary. Each build configuration can have its own combination of tool settings to precisely control how it is defined and built. Build configurations are maintained in the project Properties window in the Carbide Build Configurations panel. To open the panel, select a project in the Symbian Project Navigator or Project Explorer view and select Project > Properties or right-click and select Properties.

    -

    +

    You can select a build configuration in the Active Configuration dropdown list or use the Project > Active Configuration menu option to set which build configuration to launch when running or debugging a program. The currently selected project can be launched by clicking the Run () or Debug () control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

    If no launch configuration is present in the project, one is created on initial launch. Subsequent launches of the project will use either the last launch configuration or if more than one launch configuration exists, it uses the most correct one.

    NOTE The Carbide Run and Debug buttons are shaded in blue to indicate their behavior differs from the standard Eclipse behavior.

    @@ -35,12 +35,12 @@
    Build Configuration Naming
    -

    When the Carbide.c++ IDE creates an build configuration it uses a standard naming convention to make it easy to identify. For example, HelloCarbide S60 3.0 Emulator Debug is a typical configuration name. The default name follows the form of:

    +

    When the Carbide.c++ IDE creates an build configuration it uses a standard naming convention to make it easy to identify. For example, HelloCarbide S60 5.0 Emulator Debug is a typical configuration name. The default name follows the form of:

    You can use the Debug window to edit the default build configuration names.

    Other references
    @@ -50,7 +50,7 @@
  • Creating Launch Configurations
  • Adding/Removing Build Configurations
  • - + \ No newline at end of file