[oe-issues] [Bug 2523] OE needs a native java package

[bugzilla-daemon at tinman.treke.net]

http://bugs.openembedded.org/show_bug.cgi?id=2523





--- Comment #17 from Robert Schuster <thebohemian at gmx.net>  2007-12-19 09:57:18 ---
As discussed on the ML a pure self-hosting is desired and after some thinking I
found a way to make that happen. Here is the logical base for this - I already
have written and adjusted all the recipes in my account and am currently
compiling everything from scratch. Plenty of time to explain how it goes.

the goal:
 - we want a modern Java5-compatible runtime (think annotations) in OE
 - we want a modern Java5-compatible compiler (think generics) in OE

the problems:
 - Java5-compatible runtime needs Java5-compatible class library
 - both need a Java5-compatible compiler
 - a Java5-compiler is itself a Java application and thus needs a runtime,
class library and Java compiler, too albeit those need not to be
Java5-compatible itself

beneficial situation:
 - it exists a Java1.4 compatible compiler in OE that needs no runtime in
itself: jikes
 - this can be used to create the non-Java5 compatible initial Java-environment

the solution:
 - all the pre-Java5 stuff is called *-initial somehow
 - jikes-native builds classpath-initial, then cacao-initial and finally
ecj-initial
 - ecj-initial then builds classpath-native, cacao-native
 - ecj-bootstrap-native (a variant of ecj that is a drop-in replacement for
javac) -> voila: Java5-compatible class library, runtime and compiler :)

the recipes are a bit more complex to allow using a different initial runtime
by introducing virtual/java-initial. It is also foreseen to replace
ecj-bootstrap by another Java5-compatible compiler, the same goes for cacao as
Java5-capable runtime.


-- 
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.