Downloading phoneME Feature Software Source Code (MR4)
The phoneME Feature software project provides two ways for you to access the source code:
* Download the required phoneME Feature software zip archive files. These zip archive files include:
o The phoneME Feature download source file, phoneme_feature-mr4-rel-src-buildnum-date.zip
o The supporting emulator binary file, phoneme_feature-mr4-rel-emulator-buildnum-win-date.zip
o The supporting Qsound multimedia libraries binary file, qsound.zip
* Check out the phoneME Feature source code from the Subversion repository.
Note: If you choose to check out the phoneME Feature source code from the repository, you must install the emulator binary plugin and Qsound binary zip archive files into your source repository location.
Taken together, the phoneME Feature source files, plus the emulator and Qsound binary files, provide everything needed to build the phoneME Feature software.
Note: To build JSR 239, you also need an OpenGL ES engine. For instructions on how to build JSR 239, see the engine documentation and Sun Java Wireless Client Software Build Guide.
To check out the source code from the Subversion repository you must have a Subversion client installed on your platform. For more information on using Subversion, see the phoneME Feature Access page.
For more information on the structure of the phoneME Feature source code repository and how to work with it, see the phoneME Repository Structure page.
Downloading the Source Code Zip Archive File
To download the source code zip file, take the following steps:
1. Create a phoneME Feature directory on your platform.
% mkdir phoneME_feature
Note: Once you have created the phoneME_feature directory, you can assign it to the variable %COMPONENTS_DIR%, as described in Table 1-1.
2. Go to the phoneME Feature Downloads page and click the MR4 zip file name to copy it to your platform.
3. Once the file is downloaded, unzip the file into your phoneME_feature directory.
% unzip phoneme_feature-mr4-rel-src-buildnum-date.zip -d %COMPONENTS_DIR%
Downloading the Emulator and Qsound Binary Zip Archive Files
Once you have created the phoneME_feature directory and installed the phoneME Feature source files, follow these steps to install the emulator and Qsound libraries:
1. Go to the phoneME Feature downloads page and click the emulator binary plugin zip file name to copy it to your platform.
2. Once the file is downloaded, unzip the file into your phoneME_feature directory.
% unzip phoneme_feature-mr4-rel-emulator-buildnum-win-date.zip -d %COMPONENTS_DIR%
3. Go to the phoneME Feature downloads page and click the Qsound zip file name to copy it to your platform.
4. Once the file is downloaded, unzip the file into your phoneME_feature directory.
% unzip qsound.zip -d %COMPONENTS_DIR%
Checking Out the Source Code Repository
To check out the phoneME Feature source code repository, you must first install a Subversion client on your platform. Once the client is installed, take the following steps:
1. Create a phoneME Feature software directory on your platform and change to it.
% mkdir phoneME_feature
% cd phoneME_feature
2. Check out the source code using the following command:
% svn co https://phoneme.dev.java.net/svn/phoneme/components/component_name/trunk component_name
Note: In the phoneME Feature URL command string, component_name is the name of the component you are working with. For example, if you are checking out the MIDP component, substitute midp for component_name in both places.
3. Install the emulator binary zip archive into your source repository location.
4. Install the Qsound binary zip archive into your source repository location.
Updating the Source Code
If you are working in the phoneME Feature software source code repository, you can periodically update your code to get the latest checkins and improvements. Do the following:
1. Change to the directory for the component you want to update, for example, MIDP.
% cd phoneME_feature/midp
2. Enter the update command to update the component, as shown here.
% svn update
If you want to update other components, repeat the above steps for those components.
