Mark Murphy wrote: > > I am talking about what is possible at the SDK level, which is > presumably what you want, since you are on the beginners' list. > > Yes. It was only after I found the answer that I found out that the "beginners" list was the wrong one :-) > >> Your >> solution would link the library into the APK, which means that if I use >> it in two programs, it will be loaded into memory twice. >> > > Yes, it will. Each APK needs to be signed and sealed. > > There is no way in userland that I am aware of to achieve dynamic > linking with shared RAM. As a long time Linux programmer, your definition of "user land" is vastly different than mine. I do agree that what I want done (have done, in fact) requires changing files on /system file system, and therefor count as "platform" development. Surprisingly, it requires no cryptographic signature (of any kind). > There may be a way to achieve this via putting > your JAR in a modified firmware, as Dalvik does copy-on-write for > firmware code, though I am unclear whether that is just for the runtime > or if it includes other JARs as well. > Any JAR. The readme in the PlatformLibrary sample has the details. It is not the standard Java JAR, as it contains a classes.dex, rather than .class. > But, really, your goal should be to keep your library small, and allow > apps to statically link with it. > > Not always an option, but thanks.
Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
