Building a PCSL Reference Port (phoneME Feature MR4)

简介: Building a PCSL Reference Port (phoneME Feature MR4)   This document contains instructions for building a PCSL reference port.

Building a PCSL Reference Port (phoneME Feature 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-1Required 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. For example, USE_VS2005=true.

Building for a Windows x86 Target Platform

  1. Run the make command as a single command-line string, as shown here.

  $ 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 USE_VS2005=true 

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.

  1. Change to the PCSL directory:

  $ cd %COMPONENTS_DIR%/pcsl

  2. Run the make doc command:

  $ 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:

  $ 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 

目录
相关文章
|
Java Android开发
Rockchip系列之VendorStorage 新增framework系统jni+service接口访问(3)
Rockchip系列之VendorStorage 新增framework系统jni+service接口访问(3)
286 0
|
11月前
|
数据安全/隐私保护
【Azure Entra ID】使用PowerShell脚本导出Entra ID中指定应用下的所有用户信息
在Azure Entra ID中,需要导出一个Application 下的用户信息, 包含User的创建时间。
152 0
|
Java Android开发 芯片
使用Android Studio导入Android源码:基于全志H713 AOSP,方便解决编译、编码问题
本文介绍了如何将基于全志H713芯片的AOSP Android源码导入Android Studio以解决编译和编码问题,通过操作步骤的详细说明,展示了在Android Studio中利用代码提示和补全功能快速定位并修复编译错误的方法。
955 0
使用Android Studio导入Android源码:基于全志H713 AOSP,方便解决编译、编码问题
|
存储 编解码 API
【视频花屏问题】解码天书:深入理解视频流花屏现象及其解决方案
【视频花屏问题】解码天书:深入理解视频流花屏现象及其解决方案
2324 8
|
缓存 Java 程序员
Java基础篇----类型转换【面试题拓展】
Java基础篇----类型转换【面试题拓展】
120 1
|
数据安全/隐私保护
34Linux - 用户/权限管理(删除用户:userdel)
34Linux - 用户/权限管理(删除用户:userdel)
589 0
|
Android开发
libxxx.so- text relocations问题的终极解决方案
问题表现形式 错误或警告日志 当targetSdkVersion>=23且使用debug签名时,在6.0+的Android设备上运行App会输出以下错误Log: E/linker: /data/app/packagename/lib/arm/libxxx.
3343 0
|
移动开发 编解码 缓存
mPaas H5离线包优化指南
在移动互联网时代的今天,市场上绝大多数终端App都在使用H5展示页面,且随着终端技术迭代更新和市场多变性,H5页面在App中的占比越来越重要。同时也暴露出一个所有App的共性问题,即性能优化。同样的H5页面的性能优化也是重点问题。 在mPaaS团队中虽然已将H5页面资源等打包做离线包了,但在复杂的客户环境、开发环境、市场环境下,客户端的H5离线包仍有性能优化问题,这里整理简单了集团下对H5离线包的优化策略方案,以供参考。
3244 0
mPaas H5离线包优化指南
|
API Android开发
Android11.0(R) framework 新增类 lint 编码检查问题
Android11.0(R) framework 新增类 lint 编码检查问题
1603 0
|
Shell
解决adb shell input text 中文输入,unicode转utf-8
https://github.com/senzhk/ADBKeyBoard 上面这个是外国人写的一个输入法,我们把它安装再设置下就ok了 直接下载bin下的ADBKeyBoard.apk文件,或者上面那个网址最下端也有一个apk文件链接 第一个 1.安装 打开模拟器,adb install ADBKeyBoard.
6132 0

热门文章

最新文章