Is this requirement coming from your reading of some license (like the LGPL)? If so, it is probably not a correct reading, since most licenses do not actually *require* dynamic linking (for example, the LGPL does not require dynamic linking, it just happens to be the method most often used to fulfill one of it's disjunctive clauses).
To answer the immediate question, .dex files are not statically linked normally when produced, but are prelinked on the device by odex to everything in the bootclasspath. It is still possible to have external references in .dex files that are resolved at runtime (to .dex files not on the bootclasspath). So, effectively, the .dex files produced prior to being on the device are dynamically linked, get prelinked to stuff on the bootclasspath when put on the device, and any remaining references are resolved at runtime. So it is a mixture of static and dynamic linking. On Nov 20, 11:22 am, Nik Bhattacharya <[EMAIL PROTECTED]> wrote: > I have a requirement that any 3rd party libraries that I use in my > Android project should be dynamically linked from our source. I have > put third party jars into a lib directory and use those jars on the > classpath for my project. However, with the dex compilation process, > all of the classes are compiled into a single dex file that then gets > wrapped into the apk. Does this now constitute a "statically linked" > 3rd party library. > > Thanks, > Nik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
