gymshoe wrote: > Hi Mark, > Thanks for the comments. I will check out the GNU Classpath. > > However, I am confused. Does it matter what the size of the external > jar or library is?
Sure. For starters, Android apps can only be so big, and you really really really don't want to chew up 5MB of space just for two classes and their dependencies. The expression "trying to swat a fly with a Buick" comes to mind... > Doesn't your program just import the API's that > you tell it to from the library (and presumeably those superclasses > that it descends from)? It doesn't try to include them all does it? There is compile-time packaging, and there is loading into RAM at runtime. AFAIK, everything is included in the APK, because there is no way to know up front if you are using reflection or something and need the other classes. In terms of how classes are loaded into RAM at runtime, that's a complicated question even on "regular" Java (look up "classloaders" sometime), and I haven't the foggiest notion how Dalvik handles it on Android. So, my gut instinct still holds: it would shock and amaze me if rt.jar actually worked on Android. Now, I could be wrong -- given my surname, I'm used to things going wrong... ;-) -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Published! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
