Building and running example applications from Carbide.vs

The SDK support of Carbide.vs allows you to build S60 applications and run them in the emulator directly from the IDE. Building and running an example application for the emulator from Carbide.vs consists of the following steps:

Importing an example application to Carbide.vs

Carbide.vs allows you to import an existing S60 3rd Edition project based on its .mmp or bld.inf file. The import process does not move the project files, it creates a Visual StudioTM project that maps the existing files into Visual StudioTM. The project structure of the created Visual StudioTM project corresponds to the physical directory structure of the imported project, with the exception of files referred to by the .mmp file that do not reside in the source project directory hierarchy. These files appear under an External dependencies folder in the project.

Select either the .mmp or bld.inf file of an existing S60 3rd Edition project to import it into Microsoft® Visual StudioTM. If you select an .mmp file, a single project is imported. If you select a bld.inf file, projects are created in the same solution for each .mmp file pointed to in that bld.inf file.

To import an existing S60 3rd Edition project, open the Import Symbian Project wizard by selecting File > Import Symbian Project from the menu bar.

For more detailed information, please refer to the following topic in the Carbide.vs Help:

  • Using Carbide.vs > Importing an Existing Symbian OS Project

Creating a WINSCW build of an example application with Carbide.vs

Running an example application on the emulator is a two-step process:

  1. Build a WINSCW build of the application.

  2. Run the example application on the emulator

To create a WINSCW build of a project in Carbide.vs in order to be able to view it on the S60 emulator, do the following:

  1. Select the appropriate debug (WINSCW indicated by Deb_#, in this case "Deb_S60_32_WINSCW") build configuration from the Configuration drop-down menu in Visual Studio

  2. Start the build.

    You can use the following methods:

    • click Build > Build <project_name>

    • right-click the name of the project and select Build from the drop-down menu

The build starts. You can follow the progress of the build in the Output window.

Note: Once you start a build, wait until it has completed before continuing to work on the project. Do not select or click on any commands.

Once the build has completed, a "Done" message appears.

For more detailed information on how to create S60 3rd Edition builds in Carbide.vs, please refer to the following topic in the Carbide.vs Help:

  • Using Carbide.vs > Building a Symbian 9 Project

    Using Carbide.vs > How Tos

Running an example application in the S60 emulator from Carbide.vs

To run a WINSCW build of an example application on the emulator do the following:

  1. Choose whether you would like to debug or not.

    • If you want to debug, click Debug > Start

    • If you do not want to debug, click Debug > Start Without Debugging

  2. If the build configurations are not up-to-date, the Microsoft Development Environment dialog appears, asking you if you would like to build your project(s).

    • If you want to build, click Yes. The build runs as per normal for the project type, and the emulator then appears automatically.

    • If you do not want to build, click No. The emulator appears anyway.

    • If you decide not to run your application in an emulator, click Cancel. The dialog disappears and nothing happens.

If the build configurations are correct, the S60 emulator opens (see step 2 onwards in Launch the application in the emulator for a description of the Hello World Basic example application).

Debug mode

In debug mode, Microsoft® Visual StudioTM opens debugging tools: Autos, Locals, Watch, Call Stack, Break Points, and Command Window. It also runs the debug command in the Output window.

You can open your .cpp files and place breakpoints in them. The breakpoints provide an easy way to localize bugs by temporarily halting your program.

Removing the example application from the emulator

  1. Close the emulator.

  2. Open the solution you want to be removed in Microsoft Visual Studio.

  3. Select the SDK and its relevant build configuration to be cleaned.

    Note: The only valid build configuration for an emulator is WINS or WINSCW.

  4. Right-click the name of the solution or project.

    Note: Help files are not cleaned by this tool.

  5. Click Clean.

    The progress of the clean appears in the Output view at the bottom of the Microsoft® Visual StudioTM window.

  6. If you wish, you can check if the application has been removed. You can do one of the following:

    • Open the emulator, and check that the application no longer appears in it.

    • Open the <S60_SDK_installation_directory>\Epoc32\release\winscw\udeb\z\system\apps\ directory and check that the <ProjectName>.app or <ProjectName>.exe file has been removed (the actual file depends on the project type).