It seems a little odd that Android is supposedly "open", yet Dalvik is essentially undocumented.
On Jul 17, 8:13 am, Kostya Vasilyev <kmans...@gmail.com> wrote: > During compilation, Android tools use standard Java .class format, as > you found out. > > However, during application packaging (I think) they are converted into > Dalvik's special format, .dex, which does not use Sun's Java bytecode. > > If you list the contents of an .apk file, you will see one .dex file > instead of multiple .class files, as would be the case with a "regular" > Java application. > > http://en.wikipedia.org/wiki/Dalvik_(software) > > -- Kostya > > 17.07.2010 17:06, DanH пишет: > > > > > That's not been my impression, and when I browse an Android class file > > with a hex editor it says "CAFEBABE". > > > On Jul 16, 11:48 pm, kypriakos<demet...@ece.neu.edu> wrote: > > >> So it is fair to say = Android bytecode != 3rd party code bytecode > >> (particularly > >> from IBM or SUN or Axis)? So the reason I am not seeing the libraries > >> (which > >> otherwise helped me compile my imported app in Eclipse) in the apk > >> file > >> is because they are not recognized by the Android platform? Unless I > >> obtain > >> the source code for all those libs and try to compile and fix the > >> millions of > >> errors that will probably appear, I won't be able to use them? Is that > >> a fair > >> statement? Oh o ... > > >> Thanks > > >> On Jul 16, 4:31 pm, kypriakos<demet...@ece.neu.edu> wrote: > > >>> Hi all, > > >>> I managed to compile the imported application (the trick was not to > >>> just > >>> throw the lib directory in the project but to also build a library out > >>> of the > >>> jars and present that in the project class path). However, I am > >>> noticing > >>> in DDMS (and in debug perspective) when I launch the app that one of > >>> the > >>> threads quits and complains that: > >>> "Failed resolving Lcom/myApp/PeerToPeerAdapter: interface 211 Lnet/ > >>> wlib/PeerGen". > > >>> I can see the net/lib/PeerGen in the jar files included in the library > >>> that > >>> is in the classpath. Afterall it compiles fine. Why does it complain > >>> at runtime? Doesn't the Android plugin package what it needs in the > >>> dex, > >>> apk and res_ files before it deploys the app in the emulator? > >>> I could not find anything on this in the resources so I am wondering > >>> if > >>> anyone had this issue before - It could be trivial and I am missing > >>> something > >>> very obvious. > > >>> Thanks > > -- > Kostya Vasilev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
