BREW应用开发指南：从入门到精通

需积分: 3 145 浏览量更新于2024-08-02 收藏 404KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"这份Brew FAQ.pdf电子资料是高通公司提供的一份针对手机开发人员的重要参考资料，旨在帮助他们更好地理解和使用BREW平台进行应用开发。文档内容涵盖了多个关键领域，包括应用程序数据、地址簿、数据库与文件共享、用户界面元素如控件、日期和时间控制、对话框、菜单控制、文本和静态控件等。此外，还涉及了BREW应用的创建、编译、调试、本地化以及操作系统和处理器的兼容性问题。" 在"Application Data"部分，讨论了为什么一些原始设备制造商（OEM）会发布自己的AddrBook.h文件。这主要是因为OEM可能会扩展BREW提供的标准地址簿字段，以满足特定设备或服务的需求。BREW提供的类别和字段通常包含在AEEAddrbook.h中，而OEM自定义的扩展则体现在他们自己的头文件中。 "AddressBook"章节深入解释了OEM自定义地址簿功能的原因和适用版本，如1.1和2.0。这些自定义字段可能包括特定于OEM的服务联系信息或其他定制的通信数据，增加了应用与设备之间的集成度。在"Database & Files"和"Sharing Data, App Preferences"中，开发者可以了解到如何在BREW环境中管理数据存储、共享应用数据以及设置应用偏好，这对于创建有持久性数据和跨应用交互的应用至关重要。 "Controls"章节则详细介绍了多种用户界面元素，包括日期和时间控件、对话框、菜单控制以及文本和静态控件的使用方法，这些都是构建用户友好界面的基础。文档进一步涉及"Creating BREW Applications"，包括编译和调试过程，这对于开发者来说是实际编码阶段的关键指导。"Localizing BREW Applications"则指导开发者如何使他们的应用适应不同地区的语言和文化需求。在"Operating Systems and Processors"中，讨论了BREW应用的可移植性和与不同操作系统的兼容性问题，这对于确保应用能在各种设备上正常运行至关重要。后续章节涉及网络编程、电话API和SMS、位置定位等高级功能，以及测试、已知问题和权限管理。这些内容为开发者提供了全面的工具和信息，以便他们在BREW平台上构建高效、稳定且功能丰富的移动应用程序。这份Brew FAQ.pdf是手机开发人员不可或缺的参考资料，它详细解答了BREW开发中的常见问题，并提供了实用的技术指导。

资源详情

资源推荐

return FALSE;

}

// Set the soft key menu rectangle

IMENUCTL_SetRect(pMe->m_pISoftKey, &softKeyRect);

// Set text control title, size, properties, rectangle

ITEXTCTL_SetTitle(pMe->m_pIText, NULL, NULL, titleString);

ITEXTCTL_SetMaxSize(pMe->m_pIText, 100);

ITEXTCTL_SetProperties(pMe->m_pIText, TP_FRAME | TP_MULTILINE );

ITEXTCTL_SetRect(pMe->m_pIText, &rect);

// Initialize the softkey menu of the text control.

ITEXTCTL_SetSoftKeyMenu (pMe->m_pIText, pMe->m_pISoftKey);

// Set both the soft key and text control active.

IMENUCTL_SetActive(pMe->m_pISoftKey,TRUE);

ITEXTCTL_SetActive (pMe->m_pIText, TRUE);

In the app's HandleEvent function, you must handle the EVT_KEY and EVT_COMMAND

events as follows:

case EVT_COMMAND:

// Process EVT_COMMAND event - change of input mode

if((pMe->m_pIText != NULL) && ITEXTCTL_HandleEvent(pMe->m_pIText, eCode, wParam,

dwParam)) {

return TRUE;

}

return FALSE;

case EVT_KEY:

if ((pMe->m_pIText != NULL) && ITEXTCTL_HandleEvent(pMe->m_pIText, EVT_KEY,

wParam, dwParam)) {

//Event handled by text control

return TRUE;

}

if(pMe->m_pISoftKey != NULL && IMENUCTL_HandleEvent(pMe->m_pISoftKey, EVT_KEY,

wParam, dwParam)) {

//Event handled by menu control

return TRUE;

}

return FALSE;

f. How can I get the capital/lowercase properties for a IText Control?

Applicable Releases: 1.0, 1.1, 2.0

There is no API to determine the case of the text control string. You can convert the entire

string entered to upper or lower case by extracting the text control string, calling

WSTRUPPER() or WSTRLOWER() helper functions, and resetting the text control string.

g. How do I suppress the title area from showing on my IStatic?

Applicable Releases: 1.0, 1.1, 2.0

The title area cannot be suppressed in SDK version 1.0. In SDK 1.1 onwards, supplying a

NULL title prevents the title area from displaying.

h. How can I enable manual scrolling for my IStatic Control?

Applicable Releases: 1.0, 1.1, 2.0

Manual scrolling of IStatic control is supported in BREW SDK™ 1.1 onwards. You can enable

manual scrolling of the ISTATIC Control by following the steps below:

1) Use the ISTATIC_SetProperties() function with ST_NOSCROLL property

2) Use the ISTATIC_HandleEvent() function in the EVT_ KEY case of your applications'

HandleEvent function which processes the UP/DOWN key events for scrolling the text.

i. How do I set the background color of a IStatic control?

Applicable Releases: 1.0, 1.1, 2.0

Changing the background color of an IStatic does not work as expected in all of the current

SDK versions. When IDISPLAY_SetColor (display, CLR_USER_BACKGROUND, rgbValue) is

used to set the background color of a ISTATIC control, the following behavior is seen:

1) When the ISTATIC control is in the Manual Scroll mode (for 1.1 and 2.0 only): The

background color is not set.

2) When the ISTATIC control is in the Auto Scroll mode (for all versions): The background color

is set with the first auto scrolling movement.

This will be fixed in an upcoming version of BREW.

Creating BREW™ Applications

Compiling BREW Applications

a. What compilers can be used to compile BREW applications for the target device?

Applicable Releases: 1.0, 1.1, 2.0

The RealView™ Compilation Tools for BREW and the ARM Compiler (of which the

RealView Compilation Tools for BREW is a subset) can be used to compile BREW

applications.

The GNU compiler is also available, but not officially supported. You can find more

information on building the compiler, and download the required tools using the following

link: https://brewx.qualcomm.com/developer/extranet/support/

devtools.jsp#gcc

b. What compiler can be used to compile BREW applications for the Emulator?

Applicable Releases: 1.0, 1.1, 2.0

Any compiler that can generate a Windows DLL can be used to compile BREW

applications for BREW Emulator.

c. How do I compile an application to run on the handset?

Applicable Releases: 1.0, 1.1, 2.0

To build applications for the phone requires the RealView™ Compilation Tools for BREW,

which is used to compile and link a project that has been developed using the

PC-based

BREW SDK™, and related tools. Running an application built using the ARM tools

requires a

BREW-enabled phone, a data cable for establishing a serial connection to the

phone, and file copying software such as QUALCOMM's

BREW AppLoader application.

See

How to Build a Downloadable BREW Application for more details.

d. What guidelines should be used when compiling applications in Thumb mode?

Applicable Releases: 1.0, 1.1, 2.0

1. The function AEEMod_Load() must be moved to a different source file and this file must

be compiled in ARM mode. AEEMod_Load() must always be compiled in ARM mode.

2. All files that are compiled in thumb mode MUST have the INTERWORK compiler option

turned on. If this option is NOT turned on in the make file, then the app will very likely crash.

e. Are there any recommended steps to perform when installing the RealView™

Compilation Tools for BREW or ARM Development Suite?

When you install the ARM compiler on your machine, consider installing it to a folder

without spaces in the names. It makes it a lot easier to use the compiler on the command

line.

Also, you might want to install it to 'c:\ads', as that seems to be the location where some

things (like makefiles) default it to be. You can modify the makefiles to point to where you

want it, but it's easier not to have to do that.

For more tips, please refer to

How to Build a Downloadable BREW Application.

f. What should I do if I install the ARM compiler into a path with spaces?

Applicable Releases: 1.0, 1.1, 2.0

The solution is to modify your makefile in the following fashion: 1) Comment out the

ARMBIN, ARMINC, and ARMLIB declaration. 2) Add the full path to the ARMCC, LD, and

HEXTOOL variables. Make sure you double quote the path.

g. What is the latest release of the RealView™ Compilation Tools for BREW and

where can I obtain maintenance patches, if any?

Applicable Releases: 1.0, 1.1, 2.0

The latest version is the

RealView™ Compilation Tools for BREW. This version, which is a

free upgrade to developers who have already purchased ARM BREW Builder 1.0, is

required to support Windows XP.

ARM BREW Builder 1.0 is based on Arm Developer Suite (ADS) 1.1. Since the release of

the ARM BREW Builder 1.0, a maintenance patch for armlink (build 725) has been

released. This patch can be downloaded at

http://www.arm.com/support.nsf/html/downloads-ads11.

h. What flags should I set when compiling BREW applications to prevent static and

global data from being linked into my application?

Applicable Releases: 1.0, 1.1, 2.0

Make sure that the following flags are added to your make file. These flags will prevent

global or static data from being linked into your application.

#ARM Procedure Call Standard Options

APCS = -apcs /$(ROPI)/$(INTERWRK)/norwpi

#Linker flag

LFLAGS = $(ROPILINK) -rwpi

$(ROPI) flag is for Read-Only(code) Position independence

$(INTERWRK) is to allow ARM-Thumb interworking

$(ROPILINK) is to link image as Read-Only Position Independent

ARM 1.0 had these flags set by default, but removed this setting in 1.1. The 1.2 ADS (the

basis of the RealView™ Compilation Tools for BREW) has reverted to the 1.0 style, so the

setting of the above flags is only needed with the 1.1 ADS.

i. Does the ARM Compiler support exception handling?

Applicable Releases: 1.0, 1.1, 2.0

No, the

RealView™ Compilation Tools for BREW and the ARM Compiler (of which the

RealView Compilation Tools for BREW is a subset) do not support try/catch or exception

handling.

j. What guidelines should I follow when building the GNU compiler?

Applicable Releases: 1.0, 1.1, 2.0

When building the tool chain the most important thing is to keep other libraries out of your

build. To do this you need to make sure that your path picks up first form your compiled

directories before anything else. Common errors include unresolved external or undefined

reference to `___mempcpy'. Such errors are discussed on the BREW forum. Because we

剩余89页未读，继续阅读

liunan0507

粉丝: 3
资源: 24

BREW应用开发指南：从入门到精通

深入BREW开发.pdf

高通brew初级培训 培训资料 Brew开发技术文档.doc 海信BREW开发.pdf

Suspicious https://github.com/Homebrew/brew git origin remote found. The current git origin is: https://mirrors.ustc.edu.cn/brew.git

Error: Cannot install under Rosetta 2 in ARM default prefix (/opt/homebrew)! To rerun under ARM use: arch -arm64 brew install ... To install under x86_64, install Homebrew into /usr/local.

Error: `brew cask` is no longer a `brew` command. Use `brew <command> --cask` instead.

`brew cask` is no longer a `brew` command. Use `brew <command> --cask` instead.

python markdown怎么输入并导出成pdf

我在macOS用python想要将文件夹中的所有.doc文档转换为.pdf，并将转换后到文档另存到新的文件夹中。我已经安装了comtypes1.2.0我的python版本是3.8，代码会报错，如何解决呀，最终代码应该是

安装adb报这种错怎么解决Error: `brew cask` is no longer a `brew` command. Use `brew <command> --cask` instead.

macos 安装brew

mac输入brew update报错error

html预览pdf,从数据库导出的pdf

mac上使用国内镜像安装brew

macos 终端 卸载 brew

mac 如何安装pdf2htmlEX

brew install subversion 安装很慢

mac 卸载brew报错。curl: (7) Failed to connect to raw.githubusercontent.com port 443 after 72 ms: Couldn't connect to server

brew安装sublime怎么操作

brew 更换国内源

最新资源

高通brew初级培训培训资料 Brew开发技术文档.doc 海信BREW开发.pdf

macos 终端卸载 brew