BMP (brew mobile platform) is born.

After a while, things were not very successful, like 4.x and trigml, and after uione. BrewCommunityFinally, a new thing came out, which is BMP. It is the so-called brew mobile platform. There are many details here. If you have an account in Qualcomm, you can easily register as a BMP developer. So what is this BMP? We downloaded the SDK to find out.

This SDK version is brew MP 1.0 SDK rev 2.2. This SDK requires a lot of support, if you are developing C/C ++. You still need a lot of things:

C/C ++ Development Environment

Brew MP supports two development environments (one or both can be installed ).

1. Microsoft Visual Studio

2. Eclipse IDE for C/C ++ developers (version 3.4.0 or above)

Microsoft Visual Studio

Brew MP supports the following versions of Microsoft Visual Studio (any number of which can be installed ):

• Microsoft Visual maxcompute 2003
• Microsoft Visual Studio 2005, which requires:
  • Microsoft Visual Studio 2005 ide enhancements. Its installer can be found here Microsoft Visual Studio 2005 ide enhancements
• Microsoft Visual maxcompute 2008

To compile for a brew MP device, the following software is required:
Arm rvct2.2-www.arm.com

Of course, as the mainstream said: simple and commonly used is vs2005. Rvct (the arm compiler) and enhancement of 2005. Follow these links to download and install the SDK. Run launcher. I saw a very beautiful one:

The previous installation is not complete. Do you see the setup tab above? Click and install Visual Studio plugin. In this way, it is basically OK. After the installation is complete, open Vs and you will see that you can create BMPProgramNow

You can see that you can create brew program and brew Extension Program. Don't worry about extension anymore !!

Now let's take a look at the difference between this new thing and brew? We created an application1 project, and we were slightly disappointed thatCodeThe same as before: (Hello brew.

However, it is gratifying to note that resources are included in the file, and pre-defined statements can be included during compilation to compile the resource file first. This resource includes bar and MIF. Compiled by brx and CIF respectively. In addition, we do not need to specify the path during debugging. The new simulator will point to the path you need, without the problem of copying the MIF and DLL in the classic network, it should be said that this is the most encouraging change.

Because there is a need for extension, we also created an extension project. We can only use awesome to describe it :)

Not only is an extension project created here, but also a project for how to call it. In this way, you do not need to manually set the MIF dependencies. You do not need to copy the project and set the association. In short, you can debug this extension DLL directly. Is the world a wonderful place? :) let's take a look at the next highlights in the development process...