Setting Up for Win32, WinCE, and PalmOS Development
I mentioned earlier that MobileBuilder forces you to select a target platform when creating a new project (refer to Figure 2). Once this process has been completed, the MobileBuilder IDE will essentially act as a development environment for that target platform. For instance, if Palm is selected as the target platform, a Palm menu item appears on the main menu once the project has been created. This Palm-specific menu includes menu options for transferring application files to a Palm device, registering a Palm conduit, and running the PalmOS Emulator (POSE). Selecting the Settings option from this menu produces the dialog box shown in Figure 4. This Settings dialog allows the user to set many items common to PalmOS application development. Likewise, selecting WinCE as a target platform produces a WinCE options menu that contains options common to development projects for the Windows CE platform.
Figure 4 Settings for a Palm development project.
Once the target platform has been identified and all platform settings have been registered, you'll need to verify that your development environment is configured to compile code for the target platform. MobileBuilder itself doesn't include compilers for the wide variety of platforms it supports, leaving that task (and, possibly, that purchase) up to the software developer.
For Win32 and Windows CE development, MobileBuilder uses the Visual C++ 6.0 development tool for compilation. For PalmOS applications, MobileBuilder uses the PRC-Tools suite. For more information on tools and environment setup for MobileBuilder WinCE and Palm development, see http://www.penright.com/questions/Built-tool.htm.