On Wed, Sep 8, 2010 at 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?
Actually aidl support in library project does work in Eclipse, just not in Ant (the doc says otherwise but it works in eclipse). This is because our builder look for aidl files in *all* source folders, including the linked ones coming from library dependencies. Xav -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. 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
