Launch Configuration Filtering

-

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html

-

+ +

Creating a Launch Configuration for Emulators

diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_phone.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_phone.htm Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_phone.htm Mon Jun 21 14:53:26 2010 -0500 @@ -9,7 +9,11 @@

Symbian OS Phone Launch

-

Use the Debug As dialog to select the New Launch Configuration Wizard that will create a launch configuration for the project.

+

Use the Debug As dialog to select the New Launch Configuration Wizard that will create a launch configuration for the project. Currently there are two choices of debugger:

+

Symbian OS Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
Classic Symbian OS Reference Board Launch — uses the classic debugger engine.

Figure 1. Debug As dialog

diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor.html Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor.html Mon Jun 21 14:53:26 2010 -0500 @@ -1,52 +1,52 @@ - - -INF Editor - - - -

INF Editor - Overview Tab

- -

- The INF Editor allows you to view and modify Symbian project files and export files to be included in building your application. The settings displayed are those active for the active build configuration. However, changes made in the INF editor can be applied globally to all build configurations. Changes made in the INF editor are automatically written to the project's .INF file. You can view the .inf file by selecting the bld.inf tab located along the bottom of the INF editor.

-

- The INF Editor is shown when an INF file is - opened from the Project Explorer view or Symbian Project Navigator view by double-clicking on the file. The INF Editor is shown in Figure 1.

-

Figure 1 - INF Editor

-

- - -

Name	Function
- - Components	- - Add components such as MMP and make files to be part of the normal build process. - - Create New MMP File - creates a new MMP file at the bottom of the Component list. - Add Existing MMP File - imports a MMP file at the bottom of the Component list. - Add Existing Makefile - adds a make file to the bottom of the Component list. - Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option. - Open - Select a component and click Open to open the component in an editor window. - Up - Select a component and click Up to move the component up in the list. - Down - Select a component and click Down to move the component down in the list. - Remove - Select a component and click Remove to remove the component from the build process. -
- - Test Components -	- - Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.

Name

Function

-

- Components

-

- Add components such as MMP and make files to be part of the normal build process.

-

Create New MMP File - creates a new MMP file at the bottom of the Component list.
Add Existing MMP File - imports a MMP file at the bottom of the Component list.
Add Existing Makefile - adds a make file to the bottom of the Component list.
Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option.
Open - Select a component and click Open to open the component in an editor window.
Up - Select a component and click Up to move the component up in the list.
Down - Select a component and click Down to move the component down in the list.
Remove - Select a component and click Remove to remove the component from the build process.

-

- Test Components -

-

- Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.

-

Other references

-

- - - - - - + + +INF Editor + + + +

INF Editor - Overview Tab

+ +

+ The INF Editor allows you to view and modify Symbian project files and export files to be included in building your application. The settings displayed are those active for the active build configuration. However, changes made in the INF editor can be applied globally to all build configurations. Changes made in the INF editor are automatically written to the project's .INF file. You can view the .inf file by selecting the bld.inf tab located along the bottom of the INF editor.

+

+ The INF Editor is shown when an INF file is + opened from the Project Explorer view or Symbian Project Navigator view by double-clicking on the file. The INF Editor is shown in Figure 1.

+

Figure 1 - INF Editor

+

+ + +

Name	Function
+ + Components	+ + Add components such as MMP and make files to be part of the normal build process. + + Create New MMP File - creates a new MMP file at the bottom of the Component list. + Add Existing MMP File - imports a MMP file at the bottom of the Component list. + Add Existing Makefile - adds a make file to the bottom of the Component list. + Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option. + Open - Select a component and click Open to open the component in an editor window. + Up - Select a component and click Up to move the component up in the list. + Down - Select a component and click Down to move the component down in the list. + Remove - Select a component and click Remove to remove the component from the build process. +
+ + Test Components +	+ + Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.

Name

Function

+

+ Components

+

+ Add components such as MMP and make files to be part of the normal build process.

+

Create New MMP File - creates a new MMP file at the bottom of the Component list.
Add Existing MMP File - imports a MMP file at the bottom of the Component list.
Add Existing Makefile - adds a make file to the bottom of the Component list.
Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option.
Open - Select a component and click Open to open the component in an editor window.
Up - Select a component and click Up to move the component up in the list.
Down - Select a component and click Down to move the component down in the list.
Remove - Select a component and click Remove to remove the component from the build process.

+

+ Test Components +

+

+ Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.

+

Other references

+

+ + + + + + \ No newline at end of file diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor.html Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor.html Mon Jun 21 14:53:26 2010 -0500 @@ -10,7 +10,7 @@ The MMP Editor Overview tab allows you to view and modify your project definitions. Changes made in the MMP editor are automatically written to the project's .MMP file. You can view the .mmp file by selecting the project_name.mmp tab located along the bottom of the MMP editor.

The MMP Editor is shown when an MMP file is - opened from the Project Explorer, C/C++ Projects, or Symbian Project Navigator views. The MMP Editor is shown in Figure 1. MMP editor fields are validated for existing or correct entries. For example, if the UID 2 field is blank the label is highlighted in red. If an error exists in the mmp file, the line where the error occurs is marked and also displayed in the Problems view.

+ opened from the Project Explorer or Symbian Project Navigator views. The MMP Editor is shown in Figure 1. MMP editor fields are validated for existing or correct entries. For example, if the UID 2 field is blank the label is highlighted in red. If an error exists in the mmp file, the line where the error occurs is marked and also displayed in the Problems view.

Figure 1 - MMP Editor Overview tab

Build All Configurations

-

Select a project in the Project Explorer, C/C++ Projects, or Symbian Project Navigator view and use the Project menu or right-click to display the context menu. Select Build All Configurations (CTRL+ALT+A) to build all target build configurations enabled for the current project.

+

Select a project in the Project Explorer or Symbian Project Navigator view, then:

+

Click Project > Build All Configurations (CTRL+ALT+A) , or
Right-click the project name and select Symbian Build > Build All Configurations

+

To build all target build configurations enabled for the current project.

-

Figure 1. Build All Configurations context menu

+

Figure 1. Build All Configurations menu

Other references

Carbide Menus

Build Package (.pkg) File

Select a .pkg file in a project′s sis folder in the Project Explorer or C/C++ Projects view and right-click to display the context menu. Select Build PKG File to build the package file and create the .sis installation file. This option is also available from an editor view when the file is open. The makesis tool uses the package file and packs all the required resources together into a SIS installation file. The Console view will display the processing output. The .sis and .sisx files will appear in the sis folder.

Select a .pkg file in a project′s sis folder in the Project Explorer view and right-click to display the context menu. Select Build PKG File to build the package file and create the .sis installation file. This option is also available from an editor view when the file is open. The makesis tool uses the package file and packs all the required resources together into a SIS installation file. The Console view will display the processing output. The .sis and .sisx files will appear in the sis folder.

Figure 1. Build PKG File context menu

Other references

Clean Symbian Component

You can select a MMP or MK file in the Project Explorer, C/C++ Projects, or Symbian Project Navigator view and right-click to display the context menu. Select Clean Symbian Component (CTRL+ALT+X) to clean the selected MMP project file or makefile. You can also right-click the file in an editor view to see the same option. The cleaning process removes the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.

You can select a MMP or MK file in the Project Explorer or Symbian Project Navigator view and right-click to select Symbian Build > Clean Symbian Component (CTRL+ALT+X) to clean the selected MMP project file or makefile. You can also right-click the file in an editor view to see the same option. The cleaning process removes the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.

Figure 1. Clean Symbian Component context menu

Other references

Compile

Select a .c, .cpp, or .cia source file in the Project Explorer, C/C++ Projects, or Symbian Project Navigator view, right-click the file and choose Compile (CTRL+ALT+C) to compile it. This is also available from within a C/C++ editor view. You can use the shift or control key to select one or more of these file types across the same or different projects. The build progress is displayed in the Console view.

Select a .c, .cpp, or .cia source file in the Project Explorer or Symbian Project Navigator view, right-click the file and choose Symbian Build > Compile (CTRL+ALT+C) to compile it. This is also available from within a C/C++ editor view. You can use the shift or control key to select one or more of these file types across the same or different projects. The build progress is displayed in the Console view.

Figure 1 - Right-click to compile a source file

Other references

Project Explorer View

The Project Explorer view (Figure 1) displays relevant C/C++ projects located in the current workspace using a tree structure. Use this view to manage all the projects located in the workspace. The view is customizable and takes advantage of working sets.

Project Explorer view

The Project Explorer view (Figure 1) displays relevant C/C++ projects located in the current workspace using a tree structure. Use this view to manage all the projects located in the current workspace. The view is customizable and takes advantage of working sets.

The content of a project is dependent upon how it was created in the workspace.

Project Explorer view

Figure 1 - Project Explorer view showing projects in the current workspace

The directories that appear in the project include:

Console View

Console view

The Console view displays the output of a process and allows you to provide keyboard input to a process. There are numerous consoles available, see the Open Console dropdown list for those available to you. Most are enabled from various project panels in Carbide.

Figure 1 - Console view showing build console information

Symbian Project Navigator view

The Symbian Project Navigator view shows all files that belong to the -current build configuration. This view lists the Symbian projects in your current workspace and their corresponding *.inf file (typically bld.inf). The *.inf file contains the related MMP project files, which are also listed in a tree structure. You can collapse or expand the list for each MMP to see which sources belong to each MMP.

bld.inf

To open this view select Window > Show View > Symbian Project Navigator, or select Window > Show View > Other ... and expand the Carbide.c++ folder then choose Symbian Project Navigator.

Figure 1 shows the Symbian Project Navigator view.

Figure 1 - Symbian Project Navigator view

Table 1. Symbian Project Navigator view —shortcut menu

Table 1. Symbian Project Navigator view — shortcut menu

diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html Mon Jun 21 14:52:39 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,271 +0,0 @@ - - -Exporting project(s) to MMP/Bld.inf files in Tasks - - - - -

-

Exporting project(s) to MMP/Bld.inf files

-

- The command-line Symbian OS toolchain requires a component description - file (Bld.Inf) and one or more project definition files - (.mmp) to build a project. The export command allows you to create - these files for your projects.

-

- To export project(s) to a Bld.Inf and/or MMP - file:

-

- Click File > Export... to get a list of the - available export wizards: -
- OR
-
- Click Export from the pop-up menus of the - C/C++ Projects and Navigator views to get a - list of the available export wizards:
-
- -
-
-
Select Symbian MMP/Bld.Inf and click - Next to go to the Symbian Projects page: -
-
- -
-
-
- Select the project(s) you intend to export from the list of - Symbian Projects.
- Click Next to go to the SDKs and Build Configurations Selection page: -
- -
-
-
- Select at least one build configuration for each project in the - left-hand pane from the list of available SDKs and build configurations in the - right-hand pane. By default, all the build configurations chosen during the - last export are selected. If a project is being exported for the first time, no - build configurations are selected. -
- The build configurations chosen for a project are distinguished using - guard macros in the MMP file. The guard macros are placed around - the MMP file statements containing resources or build setting, - only valid for a subset of the chosen build configurations.
-
- There are cases where guard macros may not be able to distinguish - between two build configurations. The export wizard shows a conflict when two - such ambiguous build configurations are selected by the user.
-
- The combination of build configurations which results in a conflict - are as follows:
- -
- -
  - Any two build configurations that differ only in the build - variant (UDEB/UREL). For example, "UIQ 3.0 Phone (GCCE) Debug" and "UIQ 3.0 - Phone (GCCE) Release" configurations will result in a conflict, as they differ - only in the build variant.
  -
- -
  - Any two build configurations, of which one is user-defined based - on the other using the Manage option in the C/C++ - Build properties view of the project.
  -
  - For more information on managing build configurations, - refer to the CDT user guide.
  -
- -
- The wizard will change the build settings in the MMP - file based on the chosen build configuration. If more than one build - configuration which require different build settings are chosen, guard macros - are used to determine the build settings. For example, if you want to change - the SECUREID option for all the EKA2 build - configurations, the wizard will append the following lines into the - MMP file:
- #if def EKA2 SECUREID 0x00301 #endif - - Where EKA2 is the guard macro for all the build - configurations designed for the EKA2 kernel. The above MMP file - statements check whether the EKA2 guard macro is defined, and if - it is, change the SECUREID option accordingly. -

 
-	     
-		    Click Next to go to the MMP File and Bld.inf
-		      File page: 
-	      		    
-	        
-	       
-	      
-	        
-	           Type the MMP file location in the MMP
-		          File field, or click Browse to select the
-	           MMP file for each project listed above. 
-	           
-	             By default, the MMP file is exported to one of the
-		          following locations in the order listed below:	           
-	           
-	              The location where the project was exported the last time. 
-	              The group folder of the exported project, if it exists. 
-	              The exported project's root directory. 
-              
-	        
-	        
-	           If you select the Export Bld.inf file option, then
-		        type the Bld.Inf file location in the Bld.inf
-		          File field, or click Browse to select the
-	           Bld.Inf file. 
-	           
-	             If you do not select the Export Bld.inf file option,
-		          then you need not specify the Bld.Inf file location.	           
-	           
-	             By default, the Bld.Inf file is exported to one of the
-		           following locations in the order listed below:	           
-	           
-	             
-	               The location where the Bld.Inf was created when the
-		             project was last exported to an MMP file. 
-	              The MMP file location.
-              
-	        
-          
-	     
-       Click Next to go to the Other Makefiles page where you can specify extra Makefiles to invoke from bld.inf  
-  
-	 
-	   
-    
-       Click Next to open the Scalable Icon Makefiles page where you can specify the Makefiles used to generate scalable icon files.
-	   
-        Click Next to go to the PRJ_EXPORTS page, to specify the list of files to be copied from the source directories to
-            the releasables directories while building the project:
-            
-              
-              
-            
-          
-             Note that this page is displayed only if you have selected
-             the Export Bld.inf file option in the previous page.          
-        
-         
-            Type the Source and Target
-            locations of the file to be copied, and click Add to append
-            the source-target pair to the PRJ_EXPORTS list. You can use
-            Browse to specify the source file and its target location. If
-            the target location for the file is not specified, it will be copied to
-            epoc32\include directory. 
-          
-             Note that the contents of the PRJ_EXPORTS list is
-              exactly the same as it appears in the PRJ_EXPORTS section of the
-             Bld.Inf file.           
-        

-         
-            If you want to modify or delete any entry from the
-            PRJ_EXPORTS list, select the entry and click
-            Modify or Delete.        
-         
-            Click Next to go to the MMP Preview
-            page: 
-          
-              
-             
-       
-        
-         
-            Select a project from the list of projects to be exported, to see a
-            preview of the MMP file in the pane below. You can edit the
-            contents if required.        
-         
-            Click Finish to complete the export process. The
-            wizard will create the managed MMP file and Bld.inf
-            file in their specified locations.
-          
-             A managed MMP file contains the same content as a
-              standard MMP file would, but the contents are organised into
-              following managed sections using special tags:           
-      
-		   
-		     
-		      
-		        Binary Build Information	            
-             
-              
-                
-                  Search Path                 
-              
-              
-                
-                  Project Content Managed                 
-              
-              
-                
-                  Linkage                 
-              
-              
-                
-                  Customization                 
-              
-          
-      
-		  
-		    You will be notified in case of any errors during the updated
-		    process, which results in not creating the MMP or
-		    Bld.Inf files. 
-        
-

-


-     
-       The following MMP file generated by the wizard, shows how
-       its content is organised using managed sections:       
-     // HelloCarbide.mmp
-     /*& START_BINARY_BUILD &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     CAPABILITY READUSERDATA

-     TARGET HelloCarbide.exe

-     TARGETTYPE exe

-     UID 0x00000000 0xe4d95f85

-     VENDORID 0x00000000

-     SECUREID 0xE4D95F85

-     /*& END_BINARY_BUILD &*/
-     /*& START_SEARCH_PATHS &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     SYSTEMINCLUDE \epoc32\include \epoc32\include\variant \epoc32\include\oem

-     USERINCLUDE ..\inc ..\data

-     /*& END_SEARCH_PATHS &*/
-     /*& START_PROJECT_CONTENT &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     SOURCEPATH ..\data

-     START RESOURCE HelloCarbide.rss

-     TARGETPATH resource\apps

-     HEADER

-     END

-     START RESOURCE HelloCarbide_reg.rss

-     TARGETPATH private\10003a3f\apps

-     HEADER

-     END

-     SOURCEPATH ..\src

-     SOURCE Waving.cpp HelloCarbideDocument.cpp HelloCarbideApplication.cpp

-     SOURCE HelloCarbideAppView.cpp HelloCarbideAppUi.cpp HelloCarbide.cpp

-     /*& END_PROJECT_CONTENT &*/
-     /*& START_LINKAGE_INFORMATION &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     LIBRARY euser.lib apparc.lib cone.lib eikcore.lib avkon.lib commonengine.lib

-     LIBRARY efsrv.lib estor.lib

-     /*& END_LINKAGE_INFORMATION &*/
-   Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-

- - \ No newline at end of file diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Mon Jun 21 14:53:26 2010 -0500 @@ -49,58 +49,62 @@

Click File > Import... to get a list of available import wizards
Select Symbian OS Bld.inf file and click Next to go to the Import Bld.inf page -
- -
-
+
Select Symbian OS > Symbian OS Bld.inf file and click Next to go to the Import Bld.inf page +
- Type the location of the bld.inf file to import, or browse to the file using the Browse button.

file import

NOTE There will be two builders available in Carbide, one for SBSv1 (current version of Symbian Build System) and one for SBSv2 (newer version). The Builder option will only be displayed when a SBSv2 installation is detected.

SBSv2 only works with recent versions of Symbian OS9.5. Both SBSv1 and SBSv2 are GNU make based build systems. SBSv1 uses Perl to generate make files, while SBSv2 uses Python. Select the appropriate builder for your project.

For SBSv2, all build configurations (platform/target), including the built-in platforms (WISNCW, ARMV5), are declared in xml files in the \sbs\lib\config directory. The Build Configurations selection page will display only those kits known to support SBSv2.

Click Next to select the recognized SDKs and Build Configurations to be created for this project -
The SDKs and Build Configurations shows a tree of - the SDKs that are available to be used, and for each SDK, the type of build configurations - that are available. You can select a single SDK if you are developing the program - for just one version of a platform, or multiple SDKs if your - program is to be built against multiple platforms or operating system - versions.
-
NOTE The platforms listed are dependent upon the filter settings in the Platform Filtering Preferences.
-
-
-
-
-
Click Next to select the mmp and extension make files -
-
One MMP file must be selected in order to continue. If the bld.inf file contains more than three MMP files, just select the MMP files you need to import. If there are three or less MMP files, then all are selected for importing.
-
-
-
Click Next to enter the Project name and root directory

When creating a project, project files are created in the root directory. Carbide.c++ creates additional files for each project. They consist of:

.project - an xml file that provides a project description
.cproject - an xml file that provides additional project information
.settings folder - contains files that provide build configuration and preference settings

The root directory is a path to the root of your project. All necessary tool components, developer libraries, and information about the SDK are stored in subdirectories under this root. The whole path leading to the SDK root directory must be declared to the Windows system via the Environment Variables settings. The variable name is EPOCROOT and the variable value is the full path where a Symbian OS SDK is installed in the Windows system.

The root directory should contain all project related files that you want to work with in Carbide. The default directory is calculated by parsing the bld.inf file and mmp file(s).

Click Finish to import the project -
- The - wizard creates the project in the C/C++ Projects view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page - describes the error that occurred. If an error occurs, you must fix the project file, and then - re-import the bld.inf.
-

+ +

+
+

+

+ Type the location of the bld.inf file to import, or browse to the file using the Browse button.

Select bld.inf file to import

NOTE Depending upon which SDKs are installed, you may see both SBSv1 and SBSv2 builders available. It is recommended that SBSv2 be the primary choice as SBSv1 has been deprecated for future Symbian OS development.

SBSv2 works with recent versions of Symbian^3 and Symbian ^4 SDKs. Both SBSv1 and SBSv2 are GNU make based build systems. SBSv1 uses Perl to generate make files, while SBSv2 uses Python. Select the appropriate builder for your project.

EPOCROOT

PATH

For SBSv2, all build configurations (platform/target), including the built-in platforms (WINSCW, ARMV5), are declared in xml files in the \sbs\lib\config directory. The Build Configurations selection page displays only kits known to support SBSv2.

Click Next to select the recognized SDKs and Build Configurations to be created for this project +
+
The SDKs and Build Configurations shows a tree of + the SDKs that are available to be used, and for each SDK, the type of build configurations + that are available. You can select a single SDK if you are developing the program + for just one version of a platform, or multiple SDKs if your + program is to be built against multiple platforms or operating system + versions.
+
+

+

+
NOTE The platforms listed are dependent upon the filter settings in the Platform Filtering Preferences.
+
+

+

Click Next to select the mmp and extension make files +
+
One MMP file must be selected in order to continue. If the bld.inf file contains more than three MMP files, just select the MMP files you need to import. If there are three or less MMP files, then all are selected for importing.
+
+
+
Click Next to enter the Project name and root directory

When creating a project, project files are created in the root directory. Carbide.c++ creates additional files for each project. They consist of:

.project - an xml file that provides a project description
.cproject - an xml file that provides additional project information
.settings folder - contains files that provide build configuration and preference settings

The root directory is a path to the root of your project. All necessary tool components, developer libraries, and information about the SDK are stored in subdirectories under this root. The whole path leading to the SDK root directory must be declared to the Windows system via the Environment Variables settings. The variable name is EPOCROOT and the variable value is the full path where a Symbian OS SDK is installed in the Windows system.

The root directory should contain all project related files that you want to work with in Carbide. The default directory is calculated by parsing the bld.inf file and mmp file(s).

Click Finish to import the project +
+ The + wizard creates the project in the Project Explorer view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page + describes the error that occurred. If an error occurs, you must fix the project file, and then + re-import the bld.inf.
+

Related concepts

diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Mon Jun 21 14:53:26 2010 -0500 @@ -18,7 +18,7 @@

or

Select Run > Debug from the menu bar

Both of these methods create a new debug launch configuration if none previously existed in the project or uses the last one launched for debugging.

-

To launch using a specific debug launch configuration, right-click the project's EXE file in the C/C++ Projects view and select Debug As > Project_Name from the C/C++ Projects context menu

+

To launch using a specific debug launch configuration, right-click the project's EXE file in the Project Explorer view and select Debug As > Project_Name from the Project Explorer context menu

The debugger assumes control of the program execution as the program runs.

Enter Author and Copyright information, then click Finish.

The new defined Symbian-based class titled NewClass, is added to the project and appears in the src folder (Figure 5).

Figure 5 -New class appears in C/C++ Projects list inside the project

Figure 5 -New class appears in Project Explorer list inside the project

Related tasks

Building Projects

Building Projects and Symbian Components

Building projects consists of a new abld-based build system that wraps build functionality around existing SDK build tools that invoke makmake commands (e.g. bldmake bldfiles and abld build).

The plug-ins provide extra functionality to set up suitable build configurations for Symbian OS C++ projects. The initial selection of a build configuration is done when you create a project, as described in Creating New Projects. You can later change the Active Build Configuration. The Build Configurations also provides a command (Project > Build All Configurations) to build all the selected build configurations in a batch.

Building Symbian OS C++ projects can involve the use of Symbian OS specific tools, such as the Symbian OS resource compiler. For detailed information on such tools, see the documentation for the SDK that you are using.

You build projects to process the source files that comprise a program and - generate object code. The compiler flags syntax errors in the source files. Use the Properties for <project_name> window to control how the project is built. The following methods build a project:

Build All Configurations—builds all build configurations for a project
Build Working Set—specify which projects to build in a working set
Build Project—(CTRL+B) builds the entire project if it has never been built before or on subsequent builds only those files that have changed since the last build operation

Figure 1 - Right-click project name to build a project

-

Building a Project

-

Right-click the project name in the Project Explorer view and select Build Project (Figure 1)

-

Select the Project > Build Project menu item

-

Click the Build icon in the tool bar (Figure 2) to build the current build configuration

Figure 2 - Build icon

or -

-

Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)

-

Carbide.c++ builds the project. A build dialog and a task bar appear during a build process. All build output is shown in the Console view while build errors and warnings appear in the Problems view.

Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be - built. Carbide always checks that makefiles are up-to-date and - dependencies present.

Project is also built if you make a change to it and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.

-

When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build Console preference panel (figure 2).

-

Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.

-

Figure 4 - Build Console Preference Panel

-

Concepts

Projects

Tasks

Building Projects

Building Projects and Symbian Components

Building projects consists of a new abld-based build system that wraps build functionality around existing SDK build tools that invoke makmake commands (e.g. bldmake bldfiles and abld build).

The plug-ins provide extra functionality to set up suitable build configurations for Symbian OS C++ projects. The initial selection of a build configuration is done when you create a project, as described in Creating New Projects. You can later change the Active Build Configuration. The Build Configurations also provides a command (Project > Build All Configurations) to build all the selected build configurations in a batch.

Building Symbian OS C++ projects can involve the use of Symbian OS specific tools, such as the Symbian OS resource compiler. For detailed information on such tools, see the documentation for the SDK that you are using.

You build projects to process the source files that comprise a program and + generate object code. The compiler flags syntax errors in the source files. Use the Properties for <project_name> window to control how the project is built. The following methods build a project:

Build All Configurations—builds all build configurations for a project
Build Working Set—specify which projects to build in a working set
Build Project—(CTRL+B) builds the entire project if it has never been built before or on subsequent builds only those files that have changed since the last build operation

Figure 1 - Right-click project name to build a project

+

Building a Project

+

Right-click the project name in the Project Explorer view and select Build Project (Figure 1)

+

Select the Project > Build Project menu item

+

Click the Build icon in the tool bar (Figure 2) to build the current build configuration

Figure 2 - Build icon

or +

+

Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)

+

Carbide.c++ builds the project. A build dialog and a task bar appear during a build process. All build output is shown in the Console view while build errors and warnings appear in the Problems view.

Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be + built. Carbide always checks that makefiles are up-to-date and + dependencies present.

Project is also built if you make a change to it and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.

+

When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build Console preference panel (figure 2).

+

Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.

+

Figure 4 - Build Console Preference Panel

+

Concepts

Projects

Tasks

Building Projects

Cleaning Projects

In the Project Explorer, C/C++ Projects, or Symbian Project Navigator views you can select a project, right-click and select Clean Project (CTRL+SHIFT+-) to remove the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.

If you select a project and select the menu option Project > Clean... a Clean dialog will appear (Figure 1). You can clean all projects or select individual projects to clean. This method of cleaning projects performs the same operations as the Clean Project context menu option. If the Start a build immediately option is selected, then the selected project(s) are rebuilt after the clean operation.

Figure 1 - Clean Project Dialog

In the Project Explorer or Symbian Project Navigator views you can select a project, right-click and select Clean Project (CTRL+SHIFT+-) to remove the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.

If you select a project and select the menu option Project > Clean... the Clean dialog appears (Figure 1). You can clean all projects or select individual projects to clean within the workspace. This method of cleaning projects performs the same operations as the Clean Project context menu option. If the Start a build immediately option is selected, then the selected project(s) are rebuilt after the clean operation.

Figure 1 - Clean project options

By default, performing a Clean Project complies with the global Clean level settings in the Build preference panel and inherited by the project on creation. You can also assign project specific clean settings in the Carbide Project Settings panel in the Properties for <project> dialog.

Concepts

Projects

Tasks

Table 1. Clean dialog — options

Item

+ + + + + + + + + + + + + + + + + + + + + + + + +

Name	Function
Clean all projects	Enable to clean all the projects in the workspace.
Clean projects selected below	Enable to clean only the selected project(s).
Start a build immediately	Rebuild the selected project(s) immediately after a clean operation.
Build the entire workspace	Build the entire workspace once the clean operation is complete.
Build only the selected projects	Build only the selected projects once the clean operation is complete.

+

Other references

- + \ No newline at end of file diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Mon Jun 21 14:53:26 2010 -0500 @@ -21,7 +21,7 @@

For non-Platform Security SDKs (pre-OS 9.x), makesis is called

-

Depending upon which tool is used, you will need to complete some entries in the SIS Builder pane of the Carbide Build Configurations window of the project Properties dialog box. You can access this pane by selecting a project in the C/C++ Projects view and select Project > Properties > Carbide Build Configurations. Fill in the necessary information to add PKG files to the project for downloading.

+

Depending upon which tool is used, you will need to complete some entries in the SIS Builder pane of the Carbide Build Configurations window of the project Properties dialog box. You can access this pane by selecting a project in the Project Explorer view and select Project > Properties > Carbide Build Configurations. Fill in the necessary information to add PKG files to the project for downloading.

@@ -38,7 +38,7 @@ diff -r 9ebb7e505267 -r 30441fd93226 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_set_build_tgt.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_set_build_tgt.htm Mon Jun 21 14:52:39 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_set_build_tgt.htm Mon Jun 21 14:53:26 2010 -0500 @@ -16,7 +16,7 @@

From the toolbar

Select the project in the Project Explorer or C/C++ Projects view
Select the project in the Project Explorer view
In the toolbar click Manage configurations for the current project control () > configuration_name

Tool	SIS Properties	Complete the PKG File, and Signing Options settings in the SIS Properties dialog. By default, SIS files are output in the directory of the original SIS file. - + Figure 2 - SIS Properties dialog

Terminating a session

Symbian OS Reference Board Launch