Resources | Resources |



Brew MP application files

A Brew MP application or extension consists of the following required and optional files.

Required file types

  • Module Information File (MIF), which provides the application entry point for your application. The MIF is an application descriptor, providing information about external libraries that the application needs for execution.
  • Signature file (SIG), which is only required for the dynamic modules on a device. All Brew MP components are digitally signed. The SIG file is stored in the component's home directory; the signature spans at least the module's executable and MIF file.
  • DLL or DLL1 for Simulator, built in your development environment.
  • The Brew MP module binary file (MOD or MOD1), for devices. The MOD or MOD1 is the binary executable for a Brew MP component. It is digitally signed and stored in the component's home directory. Applications generally use the MOD module format while system components use the MOD1 format.

Optional file types

  • One or more BREW Application Resource (BAR) files. The BAR is a compiled, binary file that contains resource information. These resources are strings in menu controls, regional images, or any resource that may change based on handset, language, or region and need to be localized.
  • Any number of user files.

The following diagram shows how parts of a Brew MP application are built. An application MIF file, resource file, and application binary are created, then tested on the Brew MP Simulator. The BID files containing Brew MP ClassIDs are also included by the CIF.

Module storage

Each Brew MP component is stored in a dedicated directory in the file system rooted in either the "sys" or "user" directory. The component's home directory is the default location for all files created or accessed by the component.

Application directory structure

Brew MP introduces a single-directory module format. Legacy BREW separated MIF and MOD files. Brew MP introduces collections of files; a collection being a group of modules arranged in a similar way. The application MIF is now in the same path as the rest of the application files. Some standard Brew MP collections are pre-defined, such as those in the following table.

Name Location Module Type Description
BDS Mods fs:/mif and fs:/mod MIF and MOD Backwards compatibility with legacy BREW, Applications under development and/or test. Used for BDS application downloads
User MODs fs:/UserMods ONEDIRMOD New collection for user-installed modules. Not managed by a download system.
System MODs fs:/sys/mod ONEDIRMOD For system modules such as those that make up Brew MP itself, and those added by OEMs

Application directory

The application directory is defined as a parent directory for Brew MP applications, with each application stored in a subdirectory under this parent. Individual applications reside in subdirectories that include supporting files, such as text files, images, or data files for the application. The binary image for an application is a DLL/DLL1 file for use in the Simulator, and in a MOD/MOD1 file on the device. The application and its directory are required to have the same name. Note that the file system is case-sensitive and all file names specified with the "fs:" qualifier are treated as case-sensitive, but file names not specified with the "fs:" qualifier are treated as case-insensitive. Brew MP converts case-insensitive file names to lowercase.

A MIF contains the application's icons and therefore is best suited for only one color depth. When working with devices that don't all have the same color depth, it's usually easier to switch between different copies of the MIF than to keep modifying a single MIF. The MIF filename must match the name of the application module and its directory.