Resources | developer.brewmp.com Resources | developer.brewmp.com

Developer

resources

Include paths and environment variable changes

Brew MP introduced changes to environment variable and include paths. The Brew MP SDK introduced additional environment variables.

Include paths and environment variables in the Brew MP SDK

Due to the following changes in Brew MP, you will need to update your project files (for example, the *.sln file for Visual Studio) for your legacy BREW applications:

  • The BREWDIR environment variable has been replaced with BREWMP_PLATFORM.
  • Brew MP header files no longer contain relative paths to other include files.

In your project file, do the following:

  • Replace $(BREWDIR) with $(BREWMP_PLATFORM).
  • Update the paths for AEEModGen.c and AEEAppGen.c from $(BREWDIR)\src to $(BREWMP_PLATFORM)\system\src.
  • Update the default include paths from $(BREWDIR)\inc to $(BREWMP_PLATFORM)\system\inc.
  • Add specific include paths according to the API families (because Brew MP organizes the API headers into their corresponding family directories). For example:
    • Add $(BREWMP_PLATFORM)\ui\inc if the application uses the IDisplay interface.
    • Add $(BREWMP_PLATFORM)\media\inc if the application uses the IMedia interface. Refer to the Brew MP API Reference for more details on API families, and the APIs that each family contains.

The BREWMPSDK environment variable also exists in the Brew MP SDK, but it is recommended that BREWMP_PLATFORM be used going forward. BREWMPSDK and BREWMP_PLATFORM both contain the location of the platform directory for the current platform. BREWMPSDK contains the short name form of the path. BREWMP_PLATFORM contains the long form of the path. Use quotes around BREWMP_PLATFORM when you use it in project properties.

Include paths and environment variables in the legacy Brew MP SDK

Due to the following changes in Brew MP, you will need to update your project files (for example, the *.sln file for Visual Studio) for your legacy BREW applications:

  • The BREWDIR environment variable has been replaced with BREWMPSDK.
  • Brew MP header files no longer contain relative paths to other include files.

In your project file, do the following:

  • Replace $(BREWDIR) with $(BREWMPSDK).
  • Update the paths for AEEModGen.c and AEEAppGen.c from $(BREWDIR)\src to $(BREWMPSDK)\system\src.
  • Update the default include paths from $(BREWDIR)\inc to $(BREWMPSDK)\system\inc.
  • Add specific include paths according to the API families (because Brew MP organizes the API headers into their corresponding family directories). For example:
    • Add $(BREWMPSDK)\ui\inc if the application uses the IDisplay interface.
    • Add $(BREWMPSDK)\media\inc if the application uses the IMedia interface. Refer to the Brew MP API Reference for more details on API families, and the APIs that each family contains.

API families

The Brew MP SDK organizes files in families that correspond to functionality, as shown in the following table:
Family Includes files related to...
Connectivity Bluetooth, WIFI, WLAN, and other methods of connecting a mobile device to a wireless network.
Device Management Includes interfaces related to mobile device management including those for OMA DM, DLOTA, FOMA, and module management.
Databases Data storage on a mobile device, such as call history, personal contacts, data storage cards, database connectivity and SQL, calendars, and timezone information.
Hardware Managing the hardware of a mobile device, such as battery, camera, position determination, FM radio, joysticks, and flip-phones.
Languages Java, Adobe Flash, applet interfaces, actors (external modules that perform specific actions), and Lua.
Media Audio and visual content, including downloadable games and music, image and video files.
Networking DNS operations, multicast groups, the network subsystem on the mobile device, TCP and UDP sockets, and network connectivity.
System The Application Execution Environment (AEE), in which all Brew applets are executed, the file system, fonts, multimedia content management, players and listeners, locales, and memory management.
Telephony Telephony functionality of a mobile device, SMS messaging, and TAPI.
UI The display of the mobile device, including the way in which text and graphics are displayed, the Window Manager, and widgets that control functionality.
Addons Includes interfaces that are not part of the standard platform. Examples are Tools layers, Licensing, and Simulator APIs.

Note: If you are not sure which include paths to include for the applet, you can either include all the API family paths first and eliminate those that don't get used later or you can add the needed include paths into the project as you encounter compilation errors for the headers.