Build Recipe: Windows Mobile

Build System Setup

Required Developer Tools

Required Project Components

Building phoneME Advanced

Building Foundation Profile

Building MIDP

Runtime Examples

Foundation Profile Example

MIDP Example

The example below is based on running a MIDlet locally.

• tools

The additional required phoneME Advanced project components for building MIDP are:

• javacall
• jpeg

The additional required phoneME Advanced project components for building an optional package are:

• abstractions
• jsr[nnn]

It's best to keep each of these component directories in the same top-level directory (e.g. C:/phoneme).

Note: The following patches must be applied to the javacall directory: Copy javacall/configuration/phoneMEAdvanced/linux_x86/properties.xml to javacall/configuration/phoneMEAdvanced/wince_arm. Append the following lines to javacall/configuration/phoneMEAdvanced/wince_arm/environment.gmk: ifneq ($(USE_STATIC_PROPERTIES),true) SPECIFIC_DEFINITIONS += -DUSE_PROPERTIES_FROM_FS endif CONFIGURATION_PROPERTIES_FILE = properties.xml

Building Foundation Profile

Building MIDP

Note: The following patches must be applied to the javacall directory:

• Copy javacall/configuration/phoneMEAdvanced/linux_x86/properties.xml to javacall/configuration/phoneMEAdvanced/wince_arm.

• Append the following lines to javacall/configuration/phoneMEAdvanced/wince_arm/environment.gmk:

  ifneq ($(USE_STATIC_PROPERTIES),true)
  SPECIFIC_DEFINITIONS += -DUSE_PROPERTIES_FROM_FS
  endif
  CONFIGURATION_PROPERTIES_FILE = properties.xml
  

Required Project Components

• cdc
• javacall
• jpeg
• midp
• pcsl
• tools

It is best to keep each of these component directories in the same top-level directory (e.g. C:/phoneme).

Note:

$ mkdir C:/Documents\ and\ Settings/User/Desktop/Storage\ Card

Platform Notes

The MIDP implementation is built on top of the functionality of Foundation Profile without exposing the APIs of Foundation Profile to applications.

• • zip/unzip

• • Virtual PC 2007
  • .NET Compact Framework 2.0 SP1

export TOP_DIR="C:/pmea"

/Program Files/Microsoft Visual Studio 8/Common7/Tools/vsvars32.bat

$ export LIBPATH=

TOOLS_DIR=<location>/tools

Note: Running the build-fp.sh script should be done from the cdc/build/win32-arm-wm5 directory. Adding

cd cdc/build/win32-arm-wm5

make -C $TOP_DIR/cdc/build/win32-arm-wm5 ... (rest of make command line)

#!/bin/bash

• • diffutils

• • zip/unzip

$ sh < build-midp.sh >& err &

Using the Windows Mobile Device Emulator to Test the Executable

Using a Windows Mobile Device to Test the Executable

After testing with the Windows Mobile Device Emulator, testing with a Windows Mobile device is very straightforward. Perform the same procedures as in the previous section and use the device to mount the shared directory instead of the device emulator.

1. Create a .jar file containing a manifest file and a sample midlet.

2. Copy the .jar file to the shared folder.

3. Create a .lnk file for the midlet. It should be very similar to the .lnk file described in the previous example.

4. Create an args.txt file for the midlet:

   -Xmx2m -Dmicroedition.profiles=MIDP-2.0 -Dsun.midp.library.name=midp -Dsun.midp.home.path="\Storage Card\midp\midp_wince" -Dcom.sun.midp.mainClass.name=com.sun.midp.main.CdcMIDletSuiteLoader sun.misc.MIDPLauncher -midppath "\Storage Card\midp\midp_wince\classes" -suitepath "\Storage Card\HelloWorld.jar" -1 HelloWorld
   

5. Launch the .lnk file as in the previous example.

$ cp -r bin lib testclasses.zip /cygdrive/c/Documents\ and\ Settings/User/Desktop/Storage\ Card/

Since HelloWorld displays text on the standard output, the results of this application are not immediately apparent. Running a midlet is probably a more visually useful experiment and this will be described next.

• J2SE v 1.4.2 SDK
• Cygwin is a Linux-like environment for Windows with a package management system that allows libraries and applications to be easily downloaded and upgraded. The following Cygwin packages are necessary for development with the CDC build system on Windows XP:

• • perl

• • subversion

$ mkdir -p /mr2
$ mount C:/mr2 /mr2

export VSINSTALLDIR=$VSROOT export VCINSTALLDIR=$VSROOT/VC export VS2005_ROOT=$VSINSTALLDIR export VS8_DIR=$VSROOT2 export VS8_PATH=$VSROOT2 export VC_DIR=$VS8_DIR/VC export VC_PATH=$VS8_PATH/VC

export PATH=$VSROOT2/vc/ce/bin/x86_arm:$VSROOT2/Common7/IDE:$VSROOT2/VC/BIN:$VSROOT2/Common7/Tools:$VSROOT2/Common7/Tools/bin:$VSROOT2/VC/PlatformSDK/bin:$VSROOT2/SDK/v2.0/bin:$VSROOT2/VC/VCPackages:$PATH

#!/bin/sh

export TOP_DIR=`cygpath "C:/mr2/windows/source"`

make CVM_HOST_TOOLS_PREFIX=/usr/bin/ CVM_JAVA_TOOLS_PREFIX=`cygpath "C:/j2sdk1.4.2_15/bin/"` JDK_HOME=`cygpath "C:/j2sdk1.4.2_15"` J2ME_CLASSLIB=foundation USE_VERBOSE_MAKE=true USE_VS2005=true CVM_COMPILER_INCOMPATIBLE=false CVM_BUILD_SUBDIR=true CVM_BUILD_SUBDIR_NAME=phoneme-advanced CVM_JIT=true CVM_OPTIMIZED=true CVM_PRELOAD_LIB=true CVM_SYMBOLS=true TOOLS_DIR="$TOP_DIR"/tools ABSTRACTIONS_DIR="$TOP_DIR"/abstractions PCSL_DIR="$TOP_DIR"/pcsl USE_JPEG=true JPEG_DIR="$TOP_DIR"/jpeg USE_MIDP=true MIDP_DIR="$TOP_DIR"/midp CVM_INCLUDE_JAVACALL=false

1. Create a Windows directory named "Storage Card" and copy the appropriate CDC files into that directory. This should include the bin and lib directories and the testclasses.zip archive file.

2. Launch dvcemumanager.exe, the Microsoft Device Emulator.

1. Select the Windows Mobile 5.0 Pocket PC device emulator.

The args.txt file contains the following:

-Djava.class.path="\Storage Card\testclasses.zip" Test

Using the Windows Mobile Emulator to Test the Executable

After the build process successfully finishes, the CDC Java runtime environment is available as runtime executable located in a few target directories, most importantly the bin and lib directories. The Microsoft Device Emulator can be used to test the CDC Java runtime environment.

The first task with using the device emulator is to install the Java runtime environment within the emulator environment. While it is possible to use ActiveSync^? to do this, it is easier to use a shared folder.

1. Create a Windows directory named "Storage Card" and copy the appropriate CDC files into that directory.

1. Launch dvcemumanager.exe, the device emulator. By default, it is located in C:/Program Files/Microsoft Device Emulator/1.0.

On the emulator screen choose File->Configure. The Emulator Properties dialog displays. Under the Shared folder: edit box, select the 'Storage Card' directory you created. Click on the 'OK' button.

The folder is now shared.

Next in Windows, create a .lnk file in the Storage Card directory you just shared with the emulator to launch the CDC Java runtime environment. The paths in the .lnk file need to be relative to the Storage Card root. For example, to launch cvm:

01#"\Storage Card\bin\cvm.exe" -Djava.class.path="\Storage Card" FontTest

(NOTE:Make sure you do NOT use a drive letter prefix such as "C:\..." for the pathname of cvm.exe. There are NO drive letters on Windows Mobile, only a leading back slash "\" to indicate starting from the toplevel of the Windows Mobile Device )

In the emulator, mount the build directory as a shared folder, use the File Explorer to navigate to the storage card, and click on the .lnk file.

* 255 character limit for .lnk files

NOTE: The limit for command line length in a .lnk file is 255 characters. If you need more than this, use the following in your link file:

01#"\Storage Card\bin\cvm.exe" -f "\Storage Card\args.txt" (NOTE:Make sure you do NOT use a drive letter prefix such as "C:\..." for the pathname of cvm.exe. There are NO drive letters on Windows Mobile, only a leading back slash "\" to indicate starting from the toplevel of the Windows Mobile Device )

and create a file called args.txt. Put your command line arguments in this file. Here is an example of the formatting. Note that arguments with spaces need to be enclosed in double quotes.

-Xmx2m "-Dsun.midp.home.path=/Storage Card/midp/midp_wince" "-Dcom.sun.midp.main Class.name=com.sun.midp.main.CdcMIDletSuiteLoader" "-Xopt:stdioPrefix=\\My Documents" sun.misc.MIDPLauncher -suitepath "/Storage Card/HelloWorld.jar" "-1" "HelloWorld"

* Using option to add prefix to stdio:

"-Xopt:stdioPrefix=\\" Ex. "-Xopt:stdioPrefix=\\My Documents"

* You will also need to apply the following delta (this gets rid of the Could not read entire "-f" file error)

cdc/src/win32/bin/java_md.c on line 65, change

* fd = fopen(filename, "r"); to * fd = fopen(filename, "rb");

* Create the following files in the root "\" or "\Storage Card" directory:

OUT.txt ERR.txt IN.txt

* Using the console

Use ccregedt.exe (in the CE Remote Tools directory, usually installed under Program Files) change the initial windows mobile registry settings. Change the HKEY_LOCAL_MACHINE/Drivers/Console/OutputTo to 0 to allow cvm to write to OUT/ERR files. This registry setting defaults to a non zero value which means "disallow" - the cvm won't be able to write any console output to the ERR/OUT files.

If you want to open a console (to see console output on the fly), from the emulator, choose File->configure. In the peripherals tab, you'll see a checkbox for "Create text console window for serial port 1". Check this. It will open a console window and you'll be able to see the vm output (and other output as well). Note that this only works with version 2 of the wm5 emulator (downloaded with the link earlier on this page) - this checkbox will not be enabled with the version of the emulator that comes with the sdk download.

* Possible crash

If you see a crash like this:

OEMIoControl^?: Unsupported Code 0x1010058 - device 0x0101 func 22 OEMIoControl^?: Unsupported Code 0x1010058 - device 0x0101 func 22 CertVerify^?: \Storage Card\bin\cvm.exe trust = 2 OEMIoControl^?: Unsupported Code 0x1010058 - device 0x0101 func 22 CertVerify^?: \Storage Card\bin\cvmi.dll trust = 2 OEMIoControl^?: Unsupported Code 0x1010058 - device 0x0101 func 22 CertVerify^?: \Storage Card\bin\cvm.exe trust = 2 Data Abort: Thread=96b7674c Proc=814c7100 'cvm.exe' AKY=00010001 PC=00f33504(cvmi.dll+0x00013504) RA=00f419a8(cvmi.dll+0x000219a8) B VA=220001fc FSR=00000407

Do a soft-reset of the emulator.

* COMMAND LINE (In MS Visual Studio 2005, enter this line to the project setting [shortcut: Alt-F9] and then run the project)

• • Microsoft Device Emulator 2.0

# # Set this path for Visual Studio # VSROOT="C:/Program Files/Microsoft Visual Studio 8"

# # Set this path for Windows Mobile 5.0 Pocket PC SDK # WMROOT="C:/Program Files/Windows CE Tools/wce500/Windows Mobile 5.0 Pocket PC SDK"

export VS2005_CE_ARM_LIB="$WMROOT/Lib/ARMV4I" export VS2005_CE_ARM_INCLUDE="$WMROOT/Include/Armv4i" export VS2005_CE_ARM_PATH="$VSROOT/VC/ce/bin/x86_arm" export VS2005_COMMON_PATH="$VSROOT/VC/bin"

VSROOT2=`cygpath "$VSROOT"` export VS8_DIR="$VSROOT2"

export PATH=$VSROOT2/VC/ce/bin/x86_arm:$VSROOT2/VC/bin:$VSROOT2/Common7/Tools/Bin:$VSROOT2/Common7/IDE:$VSROOT2/Common7/Tools:$PATH

export TOP_DIR=`cygpath "C:/mr2/windows/source"`

make CVM_HOST_TOOLS_PREFIX=/usr/bin/ CVM_JAVA_TOOLS_PREFIX=`cygpath "C:/j2sdk1.4.2_15/bin/"` JDK_HOME=`cygpath "C:/j2sdk1.4.2_15"` J2ME_CLASSLIB=foundation USE_VERBOSE_MAKE=true USE_VS2005=true CVM_COMPILER_INCOMPATIBLE=false CVM_BUILD_SUBDIR=true CVM_BUILD_SUBDIR_NAME=phoneme-advanced CVM_JIT=true CVM_OPTIMIZED=true CVM_PRELOAD_LIB=true CVM_SYMBOLS=true TOOLS_DIR="$TOP_DIR"/tools

Testing the Executable

After the build process successfully finishes, the Java runtime environment is available as runtime executable located in a few directories.

CDC Build System: Windows Mobile

Building a CDC Java runtime environment for Windows Mobile requires integration of the CDC build system with conventional Windows Visual Studio developer tools.

The following sections show how to setup the CDC build system on a Windows XP host platform, and then build different versions of the CDC Java runtime environment that will also run on a Windows Mobile/Pocket PC device or emulator.

Required Developer Tools

To use the CDC build system on a Windows XP host requires three sets of developer tools:

• J2SE v 1.4.2 SDK
• Cygwin is a Linux-like environment for Windows. It includes a package management system that allows libraries and applications to be easily downloaded and upgraded. The following Cygwin packages are necessary for development with the CDC build system on Windows XP:
  • binutils
  • bison
  • flex
  • gcc-g++
  • make
  • subversion
  • zip
• Microsoft Windows Visual Studio 2005 Standard Edition is the standard tool suite for Windows development. The following service packs and SDKs are needed for development with the CDC build system on Windows XP:
  • Visual Studio 2005 SP1
  • ActiveSync^? 4.5
  • Windows Mobile 5.0 Pocket PC SDK
  • Windows Media Player 10 SDK

Getting the Project Source Code

After installing and updating the required developer tools for the CDC build system, you can get the project source code by either downloading the project source code bundle (appropriate for evaluation purposes) or checking out the project source code from the repository.

These procedures are described in Getting the Project Source Code. Both the svn and wget are available through the Cygwin package management system.

Build System Setup

With the required developer tools and project source code in place, the next step is to define a set of environment variables that describe the location of the various developer tools.

Here is a template for an environment setup script named win-setup.sh based on the default installation for the various developer tools. It's best to keep this setup script in the target build directory for Windows Mobile: cdc/build/win32-arm-wm5. It may be necessary to change the definitions of some of these locations.

add stuff here

After modifying this script it can be invoked as follows:

$ . win-setup.sh

Next, we'll need a driver script to run the build process. The following script builds a basic Foundation Profile target:

add stuff here

After modifying this script it can be invoked as follows:

$ sh < build-fp.sh >& err &

Here's a build driver script for building MIDP:

add stuff here