there has been a lot of discussions about writing native code on android,
bottom line is that some of us need native bindings.
as a fairly experienced Java developer and mobile developer, i think
i may have a starting point we can elaborate on. - and hopefully come
up with a standard solution for dong so.
Java, as a language supports native bindings using the JNI API, which
you can read up a little bit on here:
JNI: example
http://java.sun.com/developer/onlineTraining/Programming/JDCBook/jnie...
the core functional component is the use of the 'native' keyword and the
bindings to the java.lang.System.loadLibary() API, which, does seem to
be documented within the android reference:
java.lang.System
http://code.google.com/android/reference/java/lang/System.html#loadLi...)
the question here is how to build a native .so (shared library), but we
can refer to the JNI example above for instructions. we have also been
informed, through this list that you can build native code on the device,
but without UI bindings:
building native libraries (start)
http://benno.id.au/blog/2007/11/13/android-native-apps