Linked by Thom Holwerda on Tue 6th Nov 2012 23:35 UTC
In the News The desktop and laptop world is dominated by x86, the mobile/embedded world by ARM. Conventional wisdom, right? Not really. There's also MIPS - hundreds of millions of embedded devices run on MIPS, and for years now, the architecture has been trying to break into the mobile world dominated so much by ARM. They just a got a boost: MIPS has been acquired by Imagination Tech, most known for its PowerVR graphics chips used in a lot of smartphones and tablets.
Thread beginning with comment 541229
To read all comments associated with this story, please click here.
przemo_li
Member since:
2010-06-01

NATIVE (C++/C) apps for android, or apps that use native parts, will not be portable.

Its already problem with x86.

Apps writen in dalvik will run just great.

Native compiled blobs? They will need to be recompiled. And probably Google Play will have to be changed to acommodate 3 versions of each "native" app (for each architecture).

Reply Score: 1

moondevil Member since:
2005-07-08

This is a developer task, not Google's.

It is up to each developer to pack the set of shared libraries for each architecture in the .apk package.

The .apk contains the list of supported native platforms in the manifest file alongside the .so files.

Reply Parent Score: 5

dsmogor Member since:
2005-09-01

Intel partnered with Google to do on the fly Arm -> X86 recompilation serverside so even blob equipped apps could work (performance is another matter).
Googles insistence on isolating native code for compute only tasks made this approach possible.

Reply Parent Score: 4

shmerl Member since:
2010-06-08

Mer (a leading mobile GNU/Linux distro) supports MIPS just fine:

http://releases.merproject.org/releases/latest/builds/mipsel/packag...

Don't use Android - use normal mobile Linux.

Edited 2012-11-07 17:17 UTC

Reply Parent Score: 3

zima Member since:
2005-07-06

"Leading"?...

Reply Parent Score: 2