John Morrison wrote:
> For the JOS Java OS project (www.jos.org), I'm integrating: a bare-iron, x86-PC,
> native-code runtime (a.k.a., "kernel," although that's a misleading term in this
> context); a not-yet-complete C++ JVM; and a pretty lame "Hello World" program.
...
> What is the status of the classpath effort? What is my most sensible course of
> action given that status?
Virtually all of Classpath is implemented in Java, thus is machine
independent. The native I/O routines are written in C and assume a
POSIX-like environment. Big parts of java.lang and java.lang.reflect
require a VM specific implementation layer, of which the only one that
exists is for Japhar.
Your best bet is to wait for our first development release, which I expect
will be sometime around the first of the year. This should be internally
consistent and offer a minimum base level of functionality with Japhar when
running on a GNU/Linux platform. If you desire, you can go ahead and check
out the existing code from CVS, but I doubt you'll even be able to compile
it correctly.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
