Akio wrote: [...] > Is the jni interface of current android binary release code available > or not? Some of my colleges tell me the jni seems not open under > current android binary image. Thank you very much.
It is, AFAIK, not available... but it's possible to bodge it sufficiently to work. Whether it will work reliably, or whether it will *continue* to work with the next release, is another matter. Watch out for the dragons. The error reporting on System.LoadLibrary() is poor; if there are any unresolved symbols in the .so then all you'll get is an UnresolvedLinkException saying 'File Not Found'. The most common reason for *that* is because you're referring to C library or C runtime symbols that don't exist. If you go to android-developer and look for the 'Unresolved symbols & JNI' thread you'll see the various hacks I've done. Some of these might be of use to you. *Also*, there's a bug in that the shared library loader on Android fails to load shared libraries correctly under some circumstances. See #599 on the bug tracker for more information. This kicks in when you try to take the address of a member of a global structure that's not the first item. I did mention the dragons, didn't I? Good luck! -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "I have always wished for my computer to be as easy to use as my │ telephone; my wish has come true because I can no longer figure out │ how to use my telephone." --- Bjarne Stroustrup
signature.asc
Description: OpenPGP digital signature
