I meet several problems about invoking 3-party jar in our apk, or jar. As below:
1. From google's android building introduction document, it said that
local_java_library dependency only need be set in mk file in building jar
library . When building apk, this is not needed.
But, why actually I must set this dependency also in my mk file when using
a 3-party jar to building my apk? How to do to remove this dependency, but also
can build successfully, just like the framework.jar(all apk is depend on it,
but no one need set the dependency explicitly)?
2. What is the exact meaning and usage for local_static_java_library variable?
Seems it is not mentioned in android's formal document. But in mms and browser
apk, they set it in the mk file, such as
local_static_java_library:=common-android
3. For 3-party jar, if we did not put them in bootclasspath in init.rc, then in
our apk's android manifest.XML, we must add < use-library >tag to reference it,
then in runtime, system will help load the jar on demand.
Then how about for jar? Jar have no androidmanifest.XML file, if my jar
project depend on another 3-party jar and it is not added into bootclasspath ,
then how system ensure the 3-party jar is load on demand when my jar is
executed?
Thx a lot
Send from my IPad
--
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
