The chicken-and-egg problem is only relevant for distributions that have to
build Java code at the client, which it shouldn't have to do if the classes
are not machine-specific.  It should be possible to distribute as a
"pre-chickened" source distribution for machines without Java pre-installed:

(a) Java source
(b) compiled Java classes
(c) native source

Then it just uses gcc or whatever C compiler to compile the native code, and
you should be up and running no matter what your target platform.  If you
feel like it, at that point you can run javac on the Java source, but you
shouldn't have to unless there are conditional compilation directives or
something.

--John Keiser

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Brian Jones
> Sent: Wednesday, September 23, 1998 12:08 PM
> To: Wes Biggs
> Cc: [EMAIL PROTECTED]
> Subject: Re: guavac
>
>
> Wes Biggs <[EMAIL PROTECTED]> writes:
>
> > Is it not possible to have makefiles for both javac and guavac?  Aaron,
> > what in your code won't work with javac?
> >
> > >From the brief notes on the guavac page it looks like Cygnus might be
> > working toward a gcc-based java compiler.  Does anyone have any more
> > details on this?
> >
> > On second thought: Should classpath be providing a written-in-java javac
> > implementation as well (OK, not right now, but at some point down the
> > line)?  That would make sense if the Japhar/Classpath master plan is to
> > fully replace dependencies on Javasoft products. (IMO guavac is
> good, but
> > it does suffer from platform constraints more than a pure-java
> > implementation like javac does.)
> >
> > Since guavac is already C++, would there be any benefit in trying to
> > convert it to java?
> >
> > Open to your flames...
> >
> > Wes
>
> Wes,
>
> My thoughts were that to avoid a chicken and the egg problem some
> non-Java based byte compiler like guavac would be useful.  The gcj
> project Cygnus worked on is the compiler you're talking about.  It is
> supposed to be included with gcc in the near future but can be
> downloaded separately already.  I've not tried it.
>
> As to configuration, I think it should be possible to create a
> directive for automake kind of like CXX, etc. but named JAVAC which
> could be configured to whatever compiler the build host has.
>
> Brian
> --
> |-------------------------------|Software Engineer
> |Brian Jones                  |[EMAIL PROTECTED]
> |[EMAIL PROTECTED]                  |http://www.nortel.net
> |http://www.classpath.org/      |------------------------------
>
>

Reply via email to