Resources | Resources |





BREW Applet Resource file. A binary output file from the Brew MP Resource Editor or the CIFC compiler that contains the resources in one or more of the following binary formats: string, object, and binary.


The BDSMods directory on a mobile device contains BREW Distribution System (BDS) modules.


BREW Class ID file. Generated by the Brew MP ClassID Generator, it contains the ClassID.


Binary Runtime Environment for Wireless. A mobile application development platform, with versions 1.0 through BREW SDK 4.0.x, BREW is an open, extensible client platform developed by Qualcomm to support system and application software, including personalized and branded user interfaces. May be used with most wireless devices and networks. BREW is a component of the BREW System. BREW is the predecessor to Brew MP.

Brew MP

Brew Mobile Platform. A flexible operating system platform for mobile devices. Brew MP is open and extensible and works with any software ecosystem throughout the global operator and manufacturer communities. Brew MP is the successor to BREW.

Brew MP application

A self-contained software package that exposes an applet class (implements the IApplet interface) that can be loaded and executed in Brew MP Shell (or Thread), and defined in interface header files (or an IDL file if using qidl.exe).


Component application resource file. A human-readable, Lua-based source resource file that is used to generate a binary BAR file, using the CIFC compiler (cifc.exe). Defines resources that are available to the module at runtime.


Component information file. A human-readable, Lua-based source file for that is used to generate a binary MIF file, using the CIFC compiler (cifc.exe). Defines resources that a module requires to execute in the Brew MP application execution environment. The CIF format replaces the XML-based MFX file format.


Used to compile a CIF into a MIF, and a CAR into a BAR.


A user-defined type that encapsulates data and behavior (i.e., functions) to implement one or more interfaces that the class exposes.


A 32-bit, globally unique, numeric ID, typically in the form of AEECLSID_XXX, that is defined in a BID file generated by the BREW ClassID Generator. A ClassID, which is a unique ID assigned to each class when it is defined, specifies an entry subroutine that is used to create an instance of that class. A ClassID can also be used as a privilege to use the class.


Executable and linking files.


A self-contained software package that exposes one or more non-applet classes with interfaces that can be accessed by any number of Brew MP applications for extended functionality.


A goal used in the make command specifies which of the targets in the makefile will be built.


Similar to a C++ abstract base class that has only pure virtual methods that provide a specification contract that a implementing class must meet.

Interface ID

A unique ID assigned to each interface when it is defined in an interface header file (or an IDL file if using qidl.exe). Typically in the form of AEEIID_XXX.


Module information file. A binary file containing module-specific information (such as classes and privileges), and resources (such as applet names and an icon image), that a module requires at runtime. Created by compiling a module's CIF files with the CIFC compiler. Every Brew MP module requires one MIF file.


The file system format used in BREW 3.x and 4.x. MIF files are placed in fs:/mif. All other module files are placed in subdirectories of fs:/mod; the name of the subdirectory is the same as the module name.


A Brew MP module binary file. A MOD1 may contain code that is executable in all environments, including code for applets, classes used by those applets, services, and classes used by those services. See MOD.


BREW module binary file. MOPD files follow simple conventions, but may contain only code for applets and classes used by the applets. MOD files require a BREW applet context to run. See MOD1.


An executable binary file that consists of one or more components compiled into a single image.


Operational acceptance test. A test framework in the Brew MP Porting Validation Suite (PVS).


The file system format introduced in Brew MP. The MIF file is put in the same directory as the MOD, BAR, and other module files.


Porting Validation Suite. Provides platform test frameworks for Brew MP applications.

quick executable

A quick executable, or qexe, is compiled and run during the make process.


A signature file needed for dynamic modules.


The sysmods directory on a device contains system modules, which are kept in a separate directory to prevent critical system modules from being removed or overwritten.


The UserMods directory on a device contains side-loaded modules that are user managed.


A variant can be specified in the make command and indicates the target platform, such as Windows or ADS.