Building a PCSL Reference Port (MR4)

This document contains instructions for building a PCSL reference port. It has the following sections:

Building PCSL Software on a Windows x86 Build Platform
Building PCSL Documentation

PCSL libraries are used to build CLDC and the phoneME Feature software client. PCSL contains several individual services, including file, network, memory, and print. Follow the procedures in this section to build a default PCSL reference port containing libraries, tools, tests, and documentation bundles for the following target platforms:

Windows x86

Note: Although each PCSL service can be individually built, this document describes how to build the full PCSL only.

Building PCSL Software on a Windows x86 Build Platform

This section describes how to build PCSL on the Windows x86 build platform, for a JavaCall porting layer on a Windows x86 target platform, as shown in Table 3-1.

Note: Make a note of the values you choose for these variables. When building the CLDC and phoneME Feature software client, you must set corresponding values.

Setting PCSL Environment Variables for a Windows x86 Build Platform

**TABLE 3-1** Required PCSL Build Variables for Windows x86
Name	Description
`PCSL_PLATFORM`	Identifies the target operating system, the target CPU, and the compiler that the build system uses to create the PCSL library. Its value has the form os_cpu_compiler. The value of this variable is `javacall_i386_vc`. The `vc` indicates the Microsoft Visual Studio compiler.
`PCSL_OUTPUT_DIR`	Specifies the location where the build system puts PCSL output. For example, this could be `%BUILD_OUTPUT_DIR%/pcsl`.
`JAVACALL_OUTPUT_DIR`	If you are building a JavaCall porting layer implementation, this specifies the location of the JavaCall porting layer output.
`TOOLS_DIR`	Defines the directory where needed build tools are located. For example, `TOOLS_DIR=%COMPONENTS_DIR%/tools`.
`TOOLS_OUTPUT_DIR`	Defines a directory location for tools-specific output. For example, `TOOLS_OUTPUT_DIR=%BUILD_OUTPUT_SIR%/tools`.
`USE_VS2005`	Tells the build system to use Microsoft Visual Studio 2005 as the default compiler setting, as shown here: `USE_VS2005=true`. Note: If Microsoft Visual Studio 2005 is your default compiler, you do not need to set this variable. `USE_VS2005=true` is set for you in the MR4 build scripts. However, if you are using some other compiler (which is possible, but not supported, in MR4), you must set this variable to `USE_VS2005=false`.

Building for a Windows x86 Target Platform

Run the make command as a single command-line string, as shown here.
C:\> make -C %COMPONENTS_DIR%/pcsl PCSL_PLATFORM=javacall_i386_vc PCSL_OUTPUT_DIR=%BUILD_OUTPUT_DIR%/pcsl JAVACALL_OUTPUT_DIR=%BUILD_OUTPUT_DIR%/javacall TOOLS_DIR=%COMPONENTS_DIR%/tools TOOLS_OUTPUT_DIR=%BUILD_OUTPUT_DIR%/tools

The PCSL build output is found under %PCSL_OUTPUT_DIR%/javacall_i386

Building PCSL Documentation

To build Doxygen API documentation in HTML format from PCSL porting interfaces, you must install the Doxygen tool. It can be acquired from http://www.doxygen.org

Generating Doxygen Documentation

The procedure for building Doxygen documentation is the same for both Linux and Windows build platforms.

Change to the PCSL directory:
C:\> cd %COMPONENTS_DIR%/pcsl
Run the make doc command:
C:\> make doc

Note: The build system assumes that the Doxygen executable is in the directory /usr/bin/doxygen. If your executable is installed in a different location, use the DOXYGEN_CMD variable to define the new location. For example:
C:\> make DOXYGEN_CMD=doxygen_dir doc
where doxygen_dir is the location of your Doxygen executable.

Viewing PCSL Documents

Use any browser to display the Doxygen output file at the following URL:

file://%PCSL_OUTPUT_DIR%/doc/doxygen/html/index.html

first | prev | next | last