The <uses-library> element is documented at http://developer.android.com/guide/topics/manifest/uses-library-element.html.
The documentation doesn't say this explicitly, but this element is only for libraries supplied with Android. The default settings exclude a few libraries from the build's classpath. My guess is that this is done to save space. I know that you need <uses-library> for a test package, because InstrumentationTestRunner is in android.test.runner, which isn't on the classpath by default. On Sep 8, 3:29 pm, Ian Pilcher <[email protected]> wrote: > On Sep 7, 8:08 pm, Xavier Ducrohet <[email protected]> wrote: > > > In fact, this is why your install fails. The system will look for a > > *system* library named after your compile-time library. Of course it > > will fail finding it and will refuse to install your application. > > I'm not sure where I found the stuff about adding uses-library > to AndroidManifest.xml. It's definitely not where I thought it > was. I think the reason that my library project didn't work in > the first place is that I was trying to use it to share an AIDL > file between "client" and "server" projects. I've since read > that this doesn't work. > > This does raise the question, what is the "best" way to > ensure that the two projects are using the same AIDL file? > Are people just cutting and pasting? > > Thanks! -- 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
