Changeset 11354

Timestamp:

10/18/08 21:16:11 (15 years ago)

Author:

ehuelsmann

Message:

More steps toward a release:

• Mark some files with native line endings, such as README
• Edit README to reflect the current situation

Location:

trunk/j

Files:

• COPYING (modified) (1 prop)
• Makefile.in (modified) (1 prop)
• README (modified) (7 diffs, 1 prop)
• abcl.bat.in (modified) (1 prop)
• abcl.in (modified) (1 prop)
• build-abcl.lisp (modified) (1 prop)
• build.properties (modified) (1 prop)
• configure (modified) (1 prop)
• configure.ac (modified) (1 prop)
• customizations.lisp.in (modified) (2 diffs, 1 prop)
• j.bat.in (modified) (1 prop)
• j.in (modified) (1 prop)
• make-jar.bat.in (modified) (1 prop)
• make-jar.in (modified) (1 prop)

trunk/j/README

@@ -3 +3 @@
 
 Armed Bear Common Lisp is an implementation of ANSI Common Lisp that
-runs in a Java virtual machine.
+runs in a Java virtual machine.  It compiles its code to Java byte code.
 
 
@@ -10 +10 @@
 
 Armed Bear Common Lisp is distributed under the GNU General Public
-License (with a special exception described below).
+License with classpath exception (described below).
 
 A copy of GNU General Public License (GPL) is included in this
@@ -36 +36 @@
 ========
 
-To build ABCL, you'll need 
+If you want to build ABCL, you have 2 options. The first option
+applies when you come from a lisp background. The second option is more
+appropriate when you come from Java development:
 
-1)  a 1.5 JDK, 
+ I) Bootstrap ABCL using a Common Lisp implementation
+    Supported implementations for this process: SBCL, CMUCL, OpenMCL,
+    Allegro CL, LispWorks or CLISP
 
-and either 
-
-2.1) a supported Common Lisp implementation (SBCL, CMUCL, OpenMCL,
-     Allegro, LispWorks, or CLISP)
-
-or 
-
-2.2) a version of Apache Ant (post 1.7.1)
+II) Use the Ant make-like build tool for Java environments
+    The tested lowest working version is Ant 1.7.0
 
 
-Lisp-based
-----------
+In both cases you need a supported JDK version (1.5 and 1.6 have been
+tested).  Just the JRE isn't enough.
+
+
+
+I. Lisp-based build
+-------------------
 
 Copy the file 'customizations.lisp.in' to customization.lisp', in the
@@ -70 +73 @@
 Wait for the build to finish and exit the host Lisp.
 
-Use abcl.bat on Windows or ./abcl on Unix to start ABCL. (Note that
-abcl.bat and abcl contain absolute paths, so you'll need to edit the
-relevant file if you move things around after the build.)
+Use abcl.bat on Windows or ./abcl on Unix to start ABCL.
+Note: abcl.bat and abcl contain absolute paths, so you'll need
+to edit them if you move things around after the build.
 
-If the build fails in the javac stage, you might have better luck with
-this:
+In case of failure in the javac stage, you might try this:
 
     (build-abcl:build-abcl :clean t :full t :batch nil)
 
-This invokes javac separately for each .java file, which is
-considerably slower but avoids running into limitations on command
-line length.
+This invokes javac separately for each .java file, which avoids running
+into limitations on command line length (but is a lot slower).
 
-Ant-based
----------
 
-With ant-1.7.1 in your path executing 
+II. Ant-based build
+-------------------
+
+With Ant in your path, executing
 
     ant -find build.xml abcl.wrapper
 
 from the directory containing this README file will create an
-executable wrapper ('abcl' under UNIX, 'abcl.bat' under Windows) which
-can use to run ABCL.
+executable wrapper ('abcl' under UNIX, 'abcl.bat' under Windows).
+Use this wrapper to start the ABCL Java program.
 
 
@@ -98 +100 @@
 ====
 
-ABCL is a very young implementation. You are certain to encounter
-bugs.
-
-ABCL 0.0.9 fails 54 out of 21344 tests in the GCL ANSI test suite.
+A lot of (renewed) energy has been spent to make ABCL a compliant
+and practically useable Common Lisp implementation.  Because of this,
+ABCL 0.0.11 now fails only 49 out of 21344 tests in the ANSI CL test
+suite.  Next to that, the fail count of the Maxima test suite has been
+reduced from over 1400 in 0.0.10 to little more than 600 in 0.0.11.
 
 ABCL's CLOS does not handle on-the-fly redefinition of classes
@@ -111 +114 @@
 There is no MOP worth mentioning.
 
-Since this is a very early public release, there might be build
+Since this is a early public release, there might be build
 problems as well as runtime bugs.
 
@@ -120 +123 @@
 Have fun!
 
-Peter Graves
-October 18, 2005
+On behalf of all ABCL development team and contributors,
+Erik Huelsmann
+October 18, 2008

trunk/j/customizations.lisp.in

@@ -27 +27 @@
 (case *platform*
   (:windows
-   (setq *jdk*           "C:\\Program Files\\Java\\jdk1.5.0_11\\")
+   (setq *jdk*           "C:\\Program Files\\Java\\jdk1.5.0_16\\")
    #+(or) (setq *java-compiler* "jikes")
    )
@@ -35 +35 @@
    #+(or) (setq *jar*    "jar"))
   ((:linux :unknown)
-   (setq *jdk*           "/home/peter/sun/jdk1.5.0_11/")
+   (setq *jdk*           "/home/peter/sun/jdk1.5.0_16/")
    (setq *jar*           "fastjar")))