Why do you believe your two .so files belong to two different processes? Normally this will not be the case, although you can arrange for it to happen by having them loaded by two different components and assigning those components to different processes.
But from your question, it seems that is probably not the case, and something else has confused you into thinking that happened. How is b.so getting loaded? Normally, you'd link a.so against b.so and include both in the application. Then a.so can have references to locations in b.so. I think you probably won't need to know about IPC in Android. You will need to describe your problem, and what you've tried, more clearly to get any useful help, I'm afraid. On Mar 20, 5:09 am, wavelet <[email protected]> wrote: > HI All, > I am sorry to post it again. > > I am now writing a java application. On java side I use > System.loadLibrary() to load my own native shared library( named > a.so ). > I want a.so can communicate with another native shared library(named > b.so). > When a.so and b.so are loaded in the memory, they belonged to 2 > different process. > > I am not familiar with IPC in android and binder mechanism. How can I > do to make a.so communicate with b.so? > > Regards > wavelet -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
