[armedbear-cvs] r11354 - trunk/j
Erik Huelsmann
ehuelsmann at common-lisp.net
Sat Oct 18 21:16:14 UTC 2008
Author: ehuelsmann
Date: Sat Oct 18 21:16:11 2008
New Revision: 11354
Log:
More steps toward a release:
- Mark some files with native line endings, such as README
- Edit README to reflect the current situation
Modified:
trunk/j/COPYING (props changed)
trunk/j/Makefile.in (props changed)
trunk/j/README (contents, props changed)
trunk/j/abcl.bat.in (contents, props changed)
trunk/j/abcl.in (props changed)
trunk/j/build-abcl.lisp (props changed)
trunk/j/build.properties (props changed)
trunk/j/configure (props changed)
trunk/j/configure.ac (props changed)
trunk/j/customizations.lisp.in (contents, props changed)
trunk/j/j.bat.in (props changed)
trunk/j/j.in (props changed)
trunk/j/make-jar.bat.in (props changed)
trunk/j/make-jar.in (props changed)
Modified: trunk/j/README
==============================================================================
--- trunk/j/README (original)
+++ trunk/j/README Sat Oct 18 21:16:11 2008
@@ -2,14 +2,14 @@
===================
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.
LICENSE
=======
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
distribution, in the file COPYING.
@@ -35,22 +35,25 @@
BUILDING
========
-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
+II) Use the Ant make-like build tool for Java environments
+ The tested lowest working version is Ant 1.7.0
-2.1) a supported Common Lisp implementation (SBCL, CMUCL, OpenMCL,
- Allegro, LispWorks, or CLISP)
-or
+In both cases you need a supported JDK version (1.5 and 1.6 have been
+tested). Just the JRE isn't enough.
-2.2) a version of Apache Ant (post 1.7.1)
-Lisp-based
-----------
+I. Lisp-based build
+-------------------
Copy the file 'customizations.lisp.in' to customization.lisp', in the
directory containing this README file, editing to suit your situation,
@@ -69,38 +72,38 @@
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.
BUGS
====
-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
correctly, and in any event is intolerably slow. There is no support
@@ -110,7 +113,7 @@
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.
Please report problems to the j-devel mailing list:
@@ -119,5 +122,6 @@
Have fun!
-Peter Graves
-October 18, 2005
+On behalf of all ABCL development team and contributors,
+Erik Huelsmann
+October 18, 2008
Modified: trunk/j/abcl.bat.in
==============================================================================
--- trunk/j/abcl.bat.in (original)
+++ trunk/j/abcl.bat.in Sat Oct 18 21:16:11 2008
@@ -1 +1 @@
-"@JAVA@" @ABCL_JAVA_OPTIONS@ -cp "@ABCL_CLASSPATH@" org.armedbear.lisp.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
+"@JAVA@" @ABCL_JAVA_OPTIONS@ -cp "@ABCL_CLASSPATH@" org.armedbear.lisp.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
Modified: trunk/j/customizations.lisp.in
==============================================================================
--- trunk/j/customizations.lisp.in (original)
+++ trunk/j/customizations.lisp.in Sat Oct 18 21:16:11 2008
@@ -1,38 +1,38 @@
-;;; Copy this file to "customizations.lisp"
-
-;;; User customizations for the build.
-
-;;; This file is LOADed by INITIALIZE-BUILD (in build-abcl.lisp).
-
-;;; The variable *PLATFORM-IS-WINDOWS* should be true on Windows platforms. You
-;;; can, of course, substitute your own test for this in the code below, or add
-;;; a section for OS X, or Solaris, or whatever...
-
-;;; You MUST set *JDK* to the location of the JDK you want to use. Remove or
-;;; comment out settings that don't apply to your situation.
-
-;;; You don't really need to specify anything but *JDK*. *JAVA-COMPILER* and
-;;; *JAR* default to javac and jar, respectively, from the configured JDK.
-
-;;; Directories should be specified with a trailing slash (or, on Windows, a
-;;; trailing backslash).
-
-(in-package "BUILD-ABCL")
-
-;; Standard compiler options.
-(setq *javac-options* "-g")
-(setq *jikes-options* "+D -g")
-
-;; *PLATFORM* will be either :WINDOWS, :DARWIN, :LINUX, or :UNKNOWN.
-(case *platform*
- (:windows
- (setq *jdk* "C:\\Program Files\\Java\\jdk1.5.0_11\\")
- #+(or) (setq *java-compiler* "jikes")
- )
- (:darwin
- (setq *jdk* "/usr/")
- (setq *java-compiler* "jikes")
- #+(or) (setq *jar* "jar"))
- ((:linux :unknown)
- (setq *jdk* "/home/peter/sun/jdk1.5.0_11/")
- (setq *jar* "fastjar")))
+;;; Copy this file to "customizations.lisp"
+
+;;; User customizations for the build.
+
+;;; This file is LOADed by INITIALIZE-BUILD (in build-abcl.lisp).
+
+;;; The variable *PLATFORM-IS-WINDOWS* should be true on Windows platforms. You
+;;; can, of course, substitute your own test for this in the code below, or add
+;;; a section for OS X, or Solaris, or whatever...
+
+;;; You MUST set *JDK* to the location of the JDK you want to use. Remove or
+;;; comment out settings that don't apply to your situation.
+
+;;; You don't really need to specify anything but *JDK*. *JAVA-COMPILER* and
+;;; *JAR* default to javac and jar, respectively, from the configured JDK.
+
+;;; Directories should be specified with a trailing slash (or, on Windows, a
+;;; trailing backslash).
+
+(in-package "BUILD-ABCL")
+
+;; Standard compiler options.
+(setq *javac-options* "-g")
+(setq *jikes-options* "+D -g")
+
+;; *PLATFORM* will be either :WINDOWS, :DARWIN, :LINUX, or :UNKNOWN.
+(case *platform*
+ (:windows
+ (setq *jdk* "C:\\Program Files\\Java\\jdk1.5.0_16\\")
+ #+(or) (setq *java-compiler* "jikes")
+ )
+ (:darwin
+ (setq *jdk* "/usr/")
+ (setq *java-compiler* "jikes")
+ #+(or) (setq *jar* "jar"))
+ ((:linux :unknown)
+ (setq *jdk* "/home/peter/sun/jdk1.5.0_16/")
+ (setq *jar* "fastjar")))
More information about the armedbear-cvs
mailing list