Components of a BREW Application

Executable file

Windows executable (.dll)

The BREW Application executable file is a native win 32 dll file, when you compile the application using a Microsoft C/C++ compiler to run in the BREW Simulator.

ARM executable (.mod)

The BREW Application executable file is a native ARM Module file, when you compile the application using a ARM compiler to run in the Phone

MIF file (.mif)

MIF is the Module Information File of your application. As the name suggests it holds the information about your application like Applet name, Class ID, Icon, Privileges, Notification flags, dependencies etc. The MIF file is generated using the BREW MIF Editor in BREW SDK Tools folder. In later versions of MIF Editor, the file generated will have a .mfx extension, you have to compile it to get the .mif file.

BID file (.BID)

Every BREW Application will have a BID file in the name .BID, in which the applications unique Class ID is defined. The Class ID can be generated locally for development and testing from the BREW MIF Editor, but when you commercialize your application you need to generate your Class ID from Qualcomm's Website. The BID file must be included in you application .c file.

Resource file (.bar)

The Resource file contains the resources needed by your application like Strings, Images, Binary files, Objects etc. The Resource file is generated using the BREW Resource Editor in BREW SDK Tools folder. The Resource Editor will generate a .brx file, which is a XML file containing the definitions of the resources, this file is compiled to generate the .bar file.

Signature file (.sig)

The signature file is needed if you want to run your application in the phone. You can generate a signature file for your phone for from the Qualcomm's Website by entering your phones ESN. You need to be a authenticated BREW developer to generate a test signature file.