Getting started with Symbian and C ++ SDK Development

In the series 60 SDK, you can use two versions of the simulator Executable File: one version contains the symbol debugging information, and the other version is the release version. The release simulator is limited to evaluating or demonstrating only applications-it starts very quickly because it does not contain debugging information.

Both workers are called epoc.exe, but they are located in their own subdirectories. The name of the EPOC is legacy-it is the name of the operating system before the Symbian OS.

Debugging of simulators is often used in normal development activities. Depending on your ide, you can use the debugging version normally or in "debugging mode. The ability to run the same "debugging Simulator" in two modes seems a bit confusing at first.

Sometimes you may want to start the simulator, locate the application and run it, just for the purpose of testing. If a serious error occurs, the simulators and applications are closed in a constrained manner.

Sometimes you may want to set a breakpoint (breakpoint) Where you think there is a problem, and then let the IDE run the simulator in "debug mode. Then you locate the application and run it. When you interact with an application properly, a breakpoint in the code will be encountered. On the breakpoint, the source code is displayed in the IDE and all symbolic debugging information related to the application is displayed. Then, you can use the debugging feature of IDE to debug code snippets step by step under control. You can view the application source code, Data, call stack, and other debugging-related information displayed by IDE to help you track errors in code or logic.

Figure 1-3. Series 60 platform 1.2 debug the application table and List View of the simulator

Figure 1-4. helloworld application in debugging mode under Microsoft Visual C ++ ide

The executable file location of the simulator.

The Series 60 1.2 SDK release simulator is typically located below:

For visual C ++

/Symbian/6.1/series60/epoc32/release/wins/urel/epoc.exe

For Borland C ++

/Symbian/6.1/series60/epoc32/release/winsb/urel/epoc.exe

For codewarrior

/Symbian/6.1/series60/epoc32/release/winscw/urel/epoc.exe

The debugging simulator is typically located:

For visual C ++

/Symbian/6.1/series60/epoc32/release/wins/udeb/epoc.exe

For Borland C ++

/Symbian/6.1/series60/epoc32/release/winsb/udeb/epoc.exe

For codewarrior

/Symbian/6.1/series60/epoc32/release/winscw/udeb/epoc.exe

The exact path depends on the options you select when installing the SDK. In the series 60 2.x SDK, the path of the simulator is very similar-for example,/Symbian/series602_0/epoc32/release/wins/udeb/epoc.exe.

Figure 1-3 shows the Series 60 1.2 simulator. It displays the table view or list view as the main menu of the application at startup.

The shape of the phone application launched by the Series 60 2.0 simulator is similar to that of the phone application. You must navigate to the Application menu by pressing the application button 1-3 shown. Regardless of the version of Series 60, the debugging of the executable file of the simulator (udeb) is generally used as the default option of the Development Project-for example,/epoc32/release/wins/udeb/epoc.exe.

　　Simulator debugging mode

When running an application in the debugging mode of the simulator, the source code, function call stack, and variable information are immediately displayed when a code breakpoint occurs, as shown in 1-4. If the application code is not at a location that requires user input, the simulator window may disappear (it is minimized ).

Run the simulator from a command prompt

If the supervisor runs the simulator from the command line, simply open the command line and change the current supervisor to the Series 60 SDK folder where the epoc.exe application is located (for example,/Symbian/6.1/series60/epoc32/release/wins/udeb) and enter the following content:

EPOC

The above command starts the debugging simulator, and then you can locate and run your own application, but it is not in debugging mode. The application to be debugged can only run in the IDE in the debugging mode of the simulator. To run the release simulator, enter:

EPOC-rel

　　Run the simulator in Visual C ++ ide

In Visual C ++ IDE, you can press Ctrl + F5 or select build | execute epoc.exe from the menu to start the debugging version of the simulator. This will enable the simulator to be in non-debug mode. Instead, press F5 or select build | start debug | go from the menu to make the simulator in debugging mode.

When you run a visual C ++ project Simulator for the first time, a dialog box appears asking you about the executable file name. Navigate to the epoc.exe file in the SDK root directory/epoc32/release/wins/udebfolder.

　　Run the simulator in Borland C ++ Builder 6 and C ++ builderx ide

You can use the tools | mobile build Tools menu option and select Run emulator to start the debugging version of the simulator. You can also use the run | run menu option (F9), but it will cause the project to be re-created every time-and this may take a long time. When using this option, you may need to terminate the create dialog box ("Compiling") before the simulator starts ").

If you run the simulator in C ++ builderx, use the run | debug project menu option or press SHIFT + F9. If you want to recreate the project and start the simulator, select Run | run project or press F9.

　　Run the simulator in codewarrior ide

Select the project | run menu option or press Ctrl + F5 to run the simulator. Press F5 or use the project | Debug menu option to run the simulator in debug mode.

Locate and run applications Click the icon on the simulator, or use the PC keyboard cursor (arrow) to navigate and select the helloworld application. Click the "selection" button (in the middle of the cursor control key) to start the application. Note: An application without a specific icon (specified in the. AIF file) will be assigned a default icon, which looks like a jagged disk. In some sdks/IDES (such as Borland and codewarrior versions), your applications may be located in the "other" folder, not on the primary desktop. If this happens, navigate to the other folder and click "selection. In the left-side Navigation Pane, select the helloworld application and click "selection" to call the application. Figure 1-5. "helloworld" Application 　　Debug the application Instead, you can put the application running on the simulator in debugging mode in IDE-this process is verified by the IDE in use. In typical cases, you need to set a breakpoint in the appropriate position of the source code. Start the simulator in debugging mode. Because you need to debug an application (essentially a dynamic link library DLL), rather than the simulator itself, you need to navigate and run the application. The application will start and the execution will stop when the breakpoint you set is reached. Then you can use your own ide tool to gradually execute the source code of the application. 　　More ide help This article does not provide more information about different ide functions. Therefore, if you want to query more ide help information, you can use the Help menu option. For Microsoft Visual C ++, you can select the help | contents menu option, which is provided in msdn installed with IDE. For Borland C ++ Builder 6, you can use the Help menu option. In addition to the standard Borland help file, you will find an independent help | Borland C ++ mobile edition help page. For C ++ builderx, you can select help | Help topics, and then select mobile development. For metrowerks codewarrior, there is a help | online manuals menu option, which contains a large amount of valuable information when using Symbian OS. More specific ide information can be obtained online. For example, go to http://msdn.microsoft.com/chaincheck to find visual c ++ information, go to http://bdn.borland.com/chaincheck to find Borland C ++ information, and go to tracing.