3 ms·

Interesting enough, Google chose to build upon the Eclipse java compiler instead of Sun/Oracle's javac. I'm guessing this is due to javac being GPL and the Andr

by desdiv 12y ago

Interesting enough, Google chose to build upon the Eclipse java compiler instead of Sun/Oracle's javac. I'm guessing this is due to javac being GPL and the Android SDK being Apache License 2.0. This is strangely reminiscent of Apple's strong backing of LLVM. More competition and corporate funding in the compiler scene is always a good thing.

ibrahima 12y ago
Perhaps I don't pay attention to these things enough (or haven't seriously worked in Java in a while) but to me it was interesting simply to find out that Eclipse has its own Java compiler instead of using javac.
- e12e 12y ago
  For me too :-) I'm guessing, it's a reference to this: http://eclipse.org/jdt/core/ http://eclipse.org/jdt/core/ See also: http://stackoverflow.com/questions/3061654/what-is-the-difference-between-javac-and-the-eclipse-compiler http://stackoverflow.com/questions/3061654/what-is-the-diffe...
- jathak 12y ago
  I found out about it earlier this year when trying to set up Android Studio on the computers at my former high school. I couldn't figure out why I kept getting an error about the JDK being missing until I realized Eclipse had its own compiler and that's how students had been able to compile their Java code for the past four years.