Thanks, that makes sense. Also, what are the rules for AndroidManifest elements? - Does the main package or an Android library (or both) need to declare a uses-permission for something that happens in library code? - If a library implements a BroadcastReceiver should it be declared in its manifest, or that of the application (or both)? - etc.
David On Jun 22, 4:38 pm, Mike dg <vinb...@gmail.com> wrote: > Android libraries can include resources. Java libraries can not. > > On Jun 22, 8:47 am, deg <d...@degel.com> wrote: > > > > > Managing an Android project in Eclipse, which I need to divide into > > several libraries... > > > What, exactly, are the differences between "Android Libraries" (made > > with Properties | Android | Library | Add) and "Referenced > > libraries" (made with Properties | Java Build Path | Libraries | Add > > JARs). > > > I've already experimented and found out that: > > - Android Libraries cannot use other Android Libraries > > - Referenced libraries integrate less smoothly, requiring extra effort > > to build the .jar etc. > > - Both seem to be slightly unstable, sometimes not building everything > > and creating an ,apk that compiles correctly but is missing the > > library classes. (I'm not yet sure exactly when this happens, but I've > > seen it a few times -- usually fixed by closing and reopening the > > projects). > > > But, I don't yet have a good picture of when I should be using which, > > nor any overall documentation. Anyone know the full story on these two > > kinds of library usages? > > > Thanks, > > David- Hide quoted text - > > - Show quoted text - -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
