Use the Carbide Project Settings window to specify whether all components or selected subcomponents listed in a build information file (bld.inf) should be built for the currently selected project. You can also specify whether to perform a clean or reallyclean command on the project before building a project.
-
Figure 1 - Carbide Project Settings
-| Item | -Explanation | -
|---|---|
| Bld.inf file | -This is the path to the bld.inf file that lists the makefile and mmp components. | -
| Bld.inf | -Select this option to ensure all components are built for the selected project. | -
| Selected Components | -Select this option to specify which components of the bld.inf file to be built, including makefiles. The equivalent call to abld is abld build <subcomponent>. Use the Exclude extension makefiles and Exclude test components options to manage the items that appear in the list. -Toggle the state of each component to set its build state to true or not. A checkmark indicates a component is built. Click on a column title to sort the items by that columns contents. - |
-
| Exclude extension makefiles | -Toggles the presense of extension makefiles in the Selected components list. | -
| Exclude test components | -Toggles the presense of test components in the Selected components list. | -
| Enable project specific settings | -Click to set project specific build settings. By default a project in the workspace uses the global build settings unless this option is enabled. See the Build preference panel for details on these options. | -
| Configure Workspace Settings... | -Opens the Build preference panel. | -
-
Figure 2 - SBSv1 Tab
-| Item | -Explanation | -
|---|---|
| Clean level | -Specifies the level of clean to perform on project files. The levels include: -
|
-
| Manage dependency tracking | -If checked, the Symbian command line build system will not generate dependencies for source and resource files. These will be managed by Carbide. This can reduce build times. | -
| Show a dialog to modify build actions when modified MMPs are detected | -If checked, you will be asked what action to take before a build if a MMP file has been modified. -If not checked, the default action is taken for all modified mmp files. |
-
| Default action to take when mmp files are modified | -Select either None, Link only, or Compile and Link. | -
-
Figure 3 - SBSv2 Tab
-| Item | -Explanation | -
|---|---|
| Clean level | -Select the level of clean when cleaning a project.
- abld clean erases all files created by a corresponding abld target command (all intermediate files created during compilation and all executables and import libraries created by the linker) -abld reallyclean does what abld clean does, and also removes files exported by abld export and makefiles generated by abld makefile, or the abld test equivalents |
-
| Keep going | -This build option tells a particular command to keep going even if unrelated build steps report errors or files are missing. |
-
| Debug | -This option generates symbolic debug information for release or debug builds, independent of the compiler optimization level. -By default, the build system generates symbolic debug information only for the debug builds. With this option, the generation of symbolic debug information is extended to release builds to support debugging of release binaries on ARM ABI compliant platforms. |
-
| Override default make engine | -Check this box to enable an edit box to specify the make engine to use, for example, eMake from Electric Cloud. | -
-
Use the Carbide Project Settings window to specify whether all components or selected subcomponents listed in a build information file (bld.inf) should be built for the currently selected project. You can also specify whether to perform a clean or reallyclean command on the project before building a project.
+
Figure 1 - Carbide Project Settings
+| Item | +Explanation | +
|---|---|
| Bld.inf file | +This is the path to the bld.inf file that lists the makefile and mmp components. | +
| Bld.inf | +Select this option to ensure all components are built for the selected project. | +
| Selected Components | +Select this option to specify which components of the bld.inf file to be built, including makefiles. The equivalent call to abld is abld build <subcomponent>. Use the Exclude extension makefiles and Exclude test components options to manage the items that appear in the list. +Toggle the state of each component to set its build state to true or not. A checkmark indicates a component is built. Click on a column title to sort the items by that columns contents. + |
+
| Exclude extension makefiles | +Toggles the presense of extension makefiles in the Selected components list. | +
| Exclude test components | +Toggles the presense of test components in the Selected components list. | +
| Enable project specific settings | +Click to set project specific build settings. By default a project in the workspace uses the global build settings unless this option is enabled. See the Build preference panel for details on these options. | +
| Configure Workspace Settings... | +Opens the Build preference panel. | +
+
Figure 2 - SBSv1 Tab
+| Item | +Explanation | +
|---|---|
| Clean level | +Specifies the level of clean to perform on project files. The levels include: +
|
+
| Manage dependency tracking | +If checked, the Symbian command line build system will not generate dependencies for source and resource files. These will be managed by Carbide. This can reduce build times. | +
| Show a dialog to modify build actions when modified MMPs are detected | +If checked, you will be asked what action to take before a build if a MMP file has been modified. +If not checked, the default action is taken for all modified mmp files. |
+
| Default action to take when mmp files are modified | +Select either None, Link only, or Compile and Link. | +
+
Figure 3 - SBSv2 Tab
+| Item | +Explanation | +
|---|---|
| Clean level | +Select the level of clean when cleaning a project.
+
|
+
| Keep going | +This build option tells a particular command to keep going even if unrelated build steps report errors or files are missing. |
+
| Debug | +This option generates symbolic debug information for release or debug builds, independent of the compiler optimization level. +By default, the build system generates symbolic debug information only for the debug builds. With this option, the generation of symbolic debug information is extended to release builds to support debugging of release binaries on ARM ABI compliant platforms. |
+
| Override default make engine | +Check this box to enable an edit box to specify the make engine to use, for example, eMake from Electric Cloud. | +
+