I could be wrong here but I think there is something that should be pointed out about the "added libraries" situation. I also had this problem: Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY] and the threads in this email assisted in solving the problem.
The "situation" I want to point out is that when building a "standard" java application in eclipse we include the libraries necessary for the application to run. They in turn are added to the class path and/or added to the jar file as part of the application. It seems that the situation in android is slightly different. The "added" libraries are not added to the .apk file but included in the environment, i.e., in the AVD and the developer needs to construct/build it. My question: Does this mean that any and every application that needs a library like "maps.jar" file does not need to duplicate it in their environment? If one application specifies a need for the maps.jar, other application will have maps.jar available to them? Where are the specification for how libraries and resources are shared out of the "sandbox"? Thank you for any help, Lawrence On Sep 4, 9:21 am, Marco Schmitz <[email protected]> wrote: > maybe its just that simple: choose eclipse to export the library for > you. it can be found there where you can add exernal jars and stuff... > > greetings > darolla --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
