The chain I have observed is .java -> .class (.jar) -> .dex (.apk) -> odex.
.class/.jar is of course vanilla CAFEBABE stack-based JVM instructions and can be compiled with javac, eclipse etc.. .dex is Dalvik executable register-based VM, generated by using the dx tool in the SDK. .odex is optimized Dalvik executable, done upon initial startup or delivered pre-optimized...? But Java source code and byte-code are so closely related that few would fault Dick for this slip of the tongue. On May 20, 2:53 am, Michael Neale <[email protected]> wrote: > I thought the dex (?) compiler worked off the bytecode, not java > source code. The end result is of course java source ends up as dalvik > bytecode, but that isn't the mechanism and it is misleading to say > that (GWT would be more correct as it does require java source). > > Eg scala on android, jruby, groovy on android etc - all via bytecode. > > Can anyone confirm or deny this? > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" 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 > athttp://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
