Understood - addinig android.jar would hugely increase the size of your app (by about 3MB)!
I was just suggesting that you could place android.jar in your classpath for building your "coolfunctions.jar" as an alternative to creating an empty project. You would build this coolfunctions.jar outside any of your android projects. The coolfunctions.jar is then placed in the lib directory of each android application where you want to use it (which might be a single app if you only want to share it among activities as the first poster in this thread did). On Oct 8, 3:36 pm, Agus <[email protected]> wrote: > Yes, but that will increase your APK size. > you don't need to include android.jar. > > On Thu, Oct 8, 2009 at 10:49 AM, jotobjects <[email protected]> wrote: > > > Does adding the platform android.jar to the build classpath for the > > jar also make all the Android APIs accessbile? > > > On Oct 7, 7:58 am, "Mark Murphy" <[email protected]> wrote: > > > > By using an Android project to hold your JAR development, you > > > automatically get access to the Android APIs to use from your common > > code. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
