Since the Series 60 application can be established from the command prompt or IDE, we will introduce these two methods in detail. We first start using the C compiler provided by the IDE to establish analog (that is, the X86 instruction set) of the Simulator (also x86 instruction set). We simultaneously use debugging, so you can use symbol debug information and memory vulnerability check (dynamically check if the memory allocated on the stack is properly released). Open the command prompt from the command line and change the current path to the drive / folder containing the Series 60 SDK. Navigate to the folder containing the project definition (HelloWorld.MMP) and component description (BLD.INF) file - for example: / symbian / series602_0 / emccsoft / helloworld / group code for Series 60 2.x project, or / Symbian / 6.1 / series60 / emccsoft / helloworld / group The above code is used for Series 60 1.x projects. And enter: BLDMAKE BLDFILES This command is completed after a two second, and it does not have any visible output. It generates a new file abld.bat using bld.inf and helloworld.mmp file. This command file is generally generated as needed. Unlike BLD.INF and .MMP files, abld.bat cannot migrate between different IDEs and should not be modified manually. Enter the following command compile and link items:
ABLD Build Wins UDEB - Used for Visual C Abld Build Winsb UDeB - Used for the CodeWarrior Abld BUILD WINSCW UDEB - The project will be established for the Series 60 Simulator (WINS, WINSCW or WINSB) (change In order to compile and link) and contain debug information in a binary executable. Create a program project from the IDE (for example, our example helloworld application) usually establishes and runs in an IDE, so we need to use BLD.INF and HelloWorld.MMP files to establish a specific IDE project file. For Visual C , this work must be done using the tool provided by Symbian. This is optional for Borland and CodeWarrior, because both IDEs can import BLD.INF or .MMP files to establish IDE project files. When we start working from the command prompt, if the abld.bat file does not exist, it is necessary to build it; if the .mmp file or bld.inf file changes, you need to re-establish it. Enter the following contents to create an ABLD command file: BLDMAKE BLDFILES Opens the Microsoft Visual C to open the command prompt, navigate to the Drive / Item folder of the HelloWorld project, and enter: abld makefile vc6 This will build a suitable Microsoft Visual C projects and workspace files (HelloWorld.DSP and .dsw files). They will be located under the / EPOC32 / Build subfolder structure; its complete path depends on the position of the SDK, for example: / EPOC32 / Build / Emccsoft / HelloWorld / HelloWorld / Wins opens workspace files in Visual C (HelloWorld.dswor ), You can compile or link applications, which is implemented by pressing F7 or using the IDE menu option build | build helloworld.app. Use the Borland C IDE Builder 6 Create a program If you use Borland C Builder 6 mobile version (it is based on Borland C Builder 6 people version and add mobile plug-ins), you can simply put the HelloWorld project's BLD The .inf file is imported into the IDE. Use the File | New | Other menu option, then select the Import Mobile Application of the Mobile (Mobile) page in the dialog box. Browse the location of the component description file (BLD.INF) and open it. Use the Project | Make created in the Ctro F9 or menu. In order to establish and run, use Run | Run in the F9 or menu. Note that F9 or Run | Run will cause the project to re-establish each time. If you run on the simulator, use Tools | Mobile Build Tools | Run Emulator (Tools | Moving Tools | Run Simulator). IDE may prompt you to save a large number of project-related files, such as Borland project (.bpr), Borland project group (.bpg) file. The location saved by these files is the same as the folder of your BLD.INF file.
