jotobjects wrote:
> 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).
Your approach ("place android.jar in your classpath") assumes:
1. That android.jar is all you need.
2. That android.jar belongs in the classpath (vs. the bootclasspath or
something else).
There is no question that, if #1 and #2 are correct, your approach is
leaner than creating a project. I recommend creating the project simply
because #1 and #2 may not be true today and may not be true tomorrow;
using the Android build framework helps to insulate you from such changes.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy
_Beginning Android_ from Apress Now Available!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
