GCJ for eCos

Fri Jun 6 10:18:00 GMT 2003

It sounds like I should leave this be for now. My project isn't near
big enough to sponsor such an effort.
>It's a bit more complicated task than it may seem. Object, the base 
>for all java objects references Class, which references 
>ClassLoader, InputStream, etc. Soon you find out that Object alone 
>(indirectly) produces 72 dependancies, if you insist of being signature

>compatible with Sun's JDK. The good news is, that those 72 classes 
>are mostly simple, many of them being exception classes.

Perhaps a first step would be to make a list of features that 
are not needed as well as those that have to be added to support
such an environemt.
Not needed:
- interpretation(gij)
- reflection
- dynamic class loading
- the entire class library(or alternatively, but much more work,
a configurable class library along the lines of eCos approach)
These would have to be added:
- static resolution of references only. Linking must be geared 
towards throwing out all unused stuff.
Øyvind