On Fri, Oct 2, 2009 at 1:29 PM, jotobjects <[email protected]> wrote: > > This is an area that I am confused about also. The term "external > library" is perhaps overloaded with a different meaning in Android SDK > vs. in Eclipse build environment (which I don't use anyway). > Apparently this term in Android refers to a Linux platform shared > library?
Correct they are optional system-level libraries. > I think Dianne in this thread is saying that the <uses-library> is > only for shared libraries that are built-in to the device (emulator > image)? Yes. Since the maps library is Google proprietary, it's not part of the default SDK system image, and we ship a Google add-on that not only gives access to the API, but also includes a custom emulator system image that does have this system library. > And an application can NOT install a shared library? Correct. > Also I think that if you have a jar in your project lib directory that > WILL be included in the apk package? Correct in Ant, in Eclipse you have to add it to the build path. > And finally, from a recent thread, note that the maps.jar included > with the SDK is a stub for compile time linking and is NOT the > complete maps API that has to be installed on the device as a shared > library outside the application's control as mentioned above. That is correct. Like android.jar, maps.jar only contains the public API. It does not include all classes the maps library present on the system, and the included classes have no code (they all throw an exception). Xav -- Xavier Ducrohet Android SDK Tech Lead Google Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
