[Biojava-l] Minor fixes to initial codebase

[Eric Blossom]

A Makefile can be helpful for all sorts of ancillary stuff as well. Like
building JARs. One thing to try in the makefile is to find all the java
source files from a top directory, pipe that output to sed or perl to turn
those file names into Java import statements. Then javac (or jikes) the
resulting .java file. The Java compiler will take over dependency checking
from there. This allows for the build to avoid compiling things more than
once and to not miss anything.

Eric Blossom              mailto:Eric@BlossomAssociates.Com
Blossom Associates West   http://www.BlossomAssociates.Com/
                          510 841-3338

On Thu, 27 Jan 2000, Thomas Down wrote:

> Hi...
> 
> If you downloaded/checked out a copy of yesterday's BioJava
> release, I've now checked in a few minor corrections which
> should make it easier to get things compiled and built.
> 
> The current build system (builds/buildall.sh) is heavily
> Unix-oriented, and probably ought to be rethought at some
> point.  One option is normal Makefiles, but I've never
> found that these work particularly well for large Java
> projects -- I'm more inclined towards a simple pure-Java
> build driver.  Any comments?
> 
> In the mean time, it /is/ possible to build everything
> manually -- let me know if you are having any problems.
> 
> Happy hacking,
> 
> Thomas.
> -- 
> ``Science is magic that works''  -- Kurt Vonnegut.
> 
> _______________________________________________
> Biojava-l mailing list  -  Biojava-l@biojava.org
> http://biojava.org/mailman/listinfo/biojava-l
>