Re: build ideas

[Eric Blake]

I'm all for a way to compile the .class files without the shared
libraries.  I develop on a cygwin platform, which does not have the best
support for free VMs or for shared libraries, so I tend to just compile
the java files.

By the way, I think developers should have the autotools installed on
their machine, so I see no reason for CVS to keep track of generated
files like configure and Makefile.in, only the originals like
Makefile.am.  The generated files should be part of the distribution,
though, since end users should not be required to have all the developer
tools just to use the final product.  Fortunately, automake does this
correctly.

Who knows, improving the build framework might inspire someone to
improve the dependency tracking that jikes does, to make that part of
compilation even more efficient and compatible with automake.

Brian Jones wrote:
> 
> Like other GNU projects, I would like to continue to use the
> automake/autoconf system for driving the compilation of Classpath.
> For releases I'd like to continue to distribute compiled .class files
> and generated JNI headers.  I want CVS builds to generate JNI headers
> and .class files relying only on free software.  There exists a need
> within our community to generate .class files without compiling native
> libraries and I'd like that to be easier... it seems to me that to be
> successful this must be faster than 'jikes -d /tmp `find java gnu
> vm/reference -regex ".*\.java$"` or some working equivalent.

-- 
This signature intentionally left boring.

Eric Blake             address@hidden
  BYU student, free software programmer