[android-developers] Re: Deployment of native C library
Hi, your dont need your library in /system/lib, use System.load() as i already described in http://groups.google.com/group/android-developers/msg/86f49546bbab0cad Regards Volker Gropp On Nov 17, 5:05 am, adlaiti [EMAIL PROTECTED] wrote: I have a Java application that uses JNI to call a native C library (.so). This application works fine with an older version of the SDK and emulator. The library was copied to folder /system/lib on the emulator. With the current version of the emulator, that comes with Android 1.0 SDK, the folder /system/lib appears to be read-only. The message Read- only file system appears when attempting to copy the library to /system/lib. Placing a folder location in System.loadLibrary does not work; for example, System.loadLibrary(/data/misc/myCLib). Here are my questions: Is there a way to deploy my native C library to /system/lib? If not, is there some other folder that I can deploy to where loadLibrary will see it? I am using Eclipse and Ubuntu. -Aaron --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: What is google's official position on JNI ?
Hi Ranjeet, although I'm not the Android Dev Team i can tell you what ive been told last weeks about this topic: JNI is currently not supported in SDK 1.0. The reason is not quite clear, some say cause it may not work at all, or may break in the (near) future. Plus your app wont be portable and needs special versions for every hw platform. Actually i bet Android Dev Team will just tell you: native libs and JNI is not supported!. On the other hand JNI is working and Android uses it internally a lot [google talks]. But you may have problems to link against the stripped down libc they are using, or may run into other problems you cannot resolve. Plus please keep in mind there is no real solution to deploy your app on real phones, because /system/lib is read only. You might add your .so into the apk as a raw resource and extract it into your app writable directory under /data. Loading the .so works for me using System.load(). But this way the .so is stored on your phone in 2 locations, using a lot unnecessary space. Currently for a real world app on real phones i would'nt use JNI and native libs at all due to those problems. Either wait for JNI support in future SDK versions or port your library to Java. Regards Volker On Oct 1, 4:02 am, Ranjeet [EMAIL PROTECTED] wrote: Dear Android Dev Team, My apologies if I am asking a question that's already been answered. Unfortunately I haven't been able to find any documentation within Android's reference that officially states Google's position on usage of JNI/SharedObjects (written in C++ and compiled via a cross compiler) from within Java ui code. To clarify what I am trying to accomplish, we are building an application with the user interface completely written using the java/android classes/controls and it would use the shared library thats written in C++. There is just so much effort gone in to making that library that it would be a LOT of effort on our side rewriting it in Java. The library connects to our backend web server to fetch XML files over HTTP, stores some of the information from it on disk in files, and exposes the features via methods. Is this currently officially supported in Android(I have seen hello world C++ apps that run on the emulator with some security/chmod tweaks). Any information is sincerely appreciated. Thanks, -Ranjeet --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: What is google's official position on JNI ?
Hi, you may call it unfair of course. But please keep in mind, they did not tell us that they use it in their apps. But they use it in their API to delegate calls to native libs. Regards Volker On Oct 1, 11:18 am, Tauno T [EMAIL PROTECTED] wrote: Isn't it a little .. how do I say it.. unfair to tell us that JNI is not supported at all and then use it in their own apps to make them better and give them more features than are available to the rest of the developers? On Oct 1, 11:49 am, Volker Gropp [EMAIL PROTECTED] wrote: Hi Ranjeet, although I'm not the Android Dev Team i can tell you what ive been told last weeks about this topic: JNI is currently not supported in SDK 1.0. The reason is not quite clear, some say cause it may not work at all, or may break in the (near) future. Plus your app wont be portable and needs special versions for every hw platform. Actually i bet Android Dev Team will just tell you: native libs and JNI is not supported!. On the other hand JNI is working and Android uses it internally a lot [google talks]. But you may have problems to link against the stripped down libc they are using, or may run into other problems you cannot resolve. Plus please keep in mind there is no real solution to deploy your app on real phones, because /system/lib is read only. You might add your .so into the apk as a raw resource and extract it into your app writable directory under /data. Loading the .so works for me using System.load(). But this way the .so is stored on your phone in 2 locations, using a lot unnecessary space. Currently for a real world app on real phones i would'nt use JNI and native libs at all due to those problems. Either wait for JNI support in future SDK versions or port your library to Java. Regards Volker On Oct 1, 4:02 am, Ranjeet [EMAIL PROTECTED] wrote: Dear Android Dev Team, My apologies if I am asking a question that's already been answered. Unfortunately I haven't been able to find any documentation within Android's reference that officially states Google's position on usage of JNI/SharedObjects (written in C++ and compiled via a cross compiler) from within Java ui code. To clarify what I am trying to accomplish, we are building an application with the user interface completely written using the java/android classes/controls and it would use the shared library thats written in C++. There is just so much effort gone in to making that library that it would be a LOT of effort on our side rewriting it in Java. The library connects to our backend web server to fetch XML files over HTTP, stores some of the information from it on disk in files, and exposes the features via methods. Is this currently officially supported in Android(I have seen hello world C++ apps that run on the emulator with some security/chmod tweaks). Any information is sincerely appreciated. Thanks, -Ranjeet --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: qemu emulator flag not supported anymore in the 1.0 SDK?
Hi, same Problem here with the SDK1.0 emulator on Linux. Im really missing the qemu network settings to be able to use the SDK1.0. Volker Gropp On Sep 24, 5:38 pm, Cheryl Sedota [EMAIL PROTECTED] wrote: In the 1.0 SDK, trying to run: emulator.bat -qemu-m 256 on Windows XP does not work - I get this error: w: invalid option -- '-qemu' This used to work in the beta (0.9) SDK and the emulator's usage hint in the 1.0 SD indicates that the option is valid: -qemuargs... pass arguments toqemu -qemu-h displayqemuhelp Please advise. Thanks, Cheryl --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android JNI
On Aug 22, 9:30 pm, Tyler Ernst [EMAIL PROTECTED] wrote: Also since the 0.9 beta has been released I have been unable to copy the .so to the /system/lib directory of the emulator. If anyone has found a way to do this that would be greatly appreciated. Hi, you have to mount the system rw. To do so run `adb remount` before you push your .so. And keep in mind JNI will not be supported, or did you find a way to deploy your native lib with a .apk? Volker Gropp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Does Android support IMS and SIP?
On Jul 15, 1:42 pm, Jagan B [EMAIL PROTECTED] wrote: Is there any API for IMS and SIP for transfer the media files between two client applications made on Android? Hi, sadly there is no stack included. I'm working with mjSIP aswell, but experienced big performance issues and some bugs in the Code. I'm thinking about porting pjsip to android, thought media/audio will be a problem, i guess. regards, Volker Gropp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
