Comments on: Running C++ Native Applications on Android, The Final Point

By: Tim

Tim — Wed, 27 May 2009 17:11:01 +0000

Niklas Collin: What you describe is what ‘Just in Time’ compilers do. And contrary to this article it is possible to have portable C++ using LLVM. This is a virtual machine with a JIT compiler similar to the JVM or Dalvik. The difference is that it supports many more languages. JVM at least is closely tied to Java and getting C++ to compile into java/dex bytecode is tricky at best.

The real difficulty I can see with just putting LLVM on android is providing a language bindings to the android API. Not in terms of technical difficulty, but it’s probably a lot of work.

This is really needed though I think. According to one paper I read Java’s garbage collector increases RAM requirements by five times if you don’t want ridiculous performance penalties. And Dalvik currently doesn’t even have a JIT compiler!

By: huy

huy — Mon, 23 Feb 2009 02:29:20 +0000

I used arm-none-linux-gnueabi-xxx to compile. And as I knew, Android based on linux kernel, so we can start application that linux can organize. But now the problem is that
“when we start the native application (process) from Android, there’s “something” that make both the current Android application and the native application died”. I think, there must be an application on Android that supervises all of the processes that started from Android. Is it true?

By: huy

huy — Wed, 18 Feb 2009 08:33:01 +0000

I’ve got a problem:
I can start a native C application from command line on android.
I create an Android app that has a button. When I press the button,
I will call a native C function to start the native application.
The problem is that, that process of android app died. The logcat message
is like that “WIN DEATH” and the native C application cannot be started.

Please give me some suggestion.
Thanks

By: Niklas Collin

Niklas Collin — Tue, 18 Nov 2008 13:58:10 +0000

Why not just have a compiler on the phone and include C++-compilation to native code as an automatic step in the installation process? Standardized and specified properly it would work. Then you have it both ways, native code and a single source. A tool for code obfuscation could be used to make sure the source code remains closed if necessary.

By: jt

jt — Thu, 16 Oct 2008 06:50:59 +0000

We have Frameworks that help us port BREW code to WIN32, Windows Mobile, Pocket PC, and iPhone. To add Android to the list, it must support deploying of c++ apps.

By: Kookiat Suetrong

Kookiat Suetrong — Sat, 04 Oct 2008 20:43:34 +0000

very good article with rich information.

กู้เกียรติ ซื่อตรง

By: Fred

Fred — Wed, 01 Oct 2008 19:01:51 +0000

As far as I know.. the Andriod isn’t running an MSM chipset but an OMAP 3430 which features an ARM A-8 Cortex CPU capable of SIMD instructions, vector floating point, MMX like instructions and even has the PowerVR SBX video chip on there which allows for vertex/pixel shaders!

By: imran tanveer

imran tanveer — Sun, 11 May 2008 05:52:15 +0000

i want to know that can i run my c++’s code in mobile.

By: Do Android dream of something more than Java? « Mantrid’s Weblog

Do Android dream of something more than Java? « Mantrid’s Weblog — Mon, 28 Apr 2008 08:53:57 +0000

[...] There is however a lot of doubt about these attempts. Even a discussion arose on Google Groups. One of main concerns is such native code has to be compiled for every device out there that is going to run Android to make it fully supported. And Android was created to eliminate the need to recompile stuff. Hatem Ben Yacoub of Open Handset Magazine has addressed the issue here. [...]

By: Jeśli nie Java, to co? Czyli inne języki programowania na platofrmę Android : GPhone - Platforma Google Android, Open Social. API, Programowanie, Nowoczesne Telefony Komórkowe, Iphone

Mon, 28 Apr 2008 08:45:39 +0000

[...] Hatem Ben Yacoub z Open Handset Magazine poddał w wątpliwość takie próby. [...]