source: tags/0.13.0/abcl/README

Last change on this file was 11670, checked in by Mark Evenson, 15 years ago

Continued iteration of documentation for release.

  • Property svn:eol-style set to native
File size: 4.3 KB
Line 
1GENERAL INFORMATION
2===================
3
4ABCL (Armed Bear Common Lisp) is an implementation of ANSI Common Lisp
5that runs in a Java virtual machine.  It compiles its code to Java
6byte code.
7
8
9LICENSE
10=======
11
12Armed Bear Common Lisp is distributed under the GNU General Public
13License with classpath exception (described below).
14
15A copy of GNU General Public License (GPL) is included in this
16distribution, in the file COPYING.
17
18Linking this software statically or dynamically with other modules is
19making a combined work based on this software. Thus, the terms and
20conditions of the GNU General Public License cover the whole
21combination.
22
23As a special exception, the copyright holders of this software give
24you permission to link this software with independent modules to
25produce an executable, regardless of the license terms of these
26independent modules, and to copy and distribute the resulting
27executable under terms of your choice, provided that you also meet,
28for each linked independent module, the terms and conditions of the
29license of that module. An independent module is a module which is not
30derived from or based on this software. If you modify this software,
31you may extend this exception to your version of the software, but you
32are not obligated to do so. If you do not wish to do so, delete this
33exception statement from your version.
34
35
36BUILDING
37========
38
39If you want to build ABCL, you have 3 options. The first option
40applies when you come from a Lisp background. The second and thirds
41options are more appropriate when you come from Java development:
42
43 I)  Bootstrap ABCL using a Common Lisp implementation Supported
44     implementations for this process: SBCL, CMUCL, OpenMCL, Allegro
45     CL, LispWorks or CLISP.
46
47II)  Use the Ant make-like build tool for Java environments
48     The tested lowest working version is Ant 1.7.0. 
49
50III) Use the Netbeans 6.x IDE to open ABCL as a project.
51
52
53In both cases you need a supported JDK version (1.5 and 1.6 have been
54tested).  Just the JRE isn't enough.
55
56
57
58I. Lisp-based build
59-------------------
60
61Copy the file 'customizations.lisp.in' to customization.lisp', in the
62directory containing this README file, editing to suit your situation,
63paying attention to the comments in the file.
64
65Start up one of the supported Common Lisp implementations in the
66directory containing this README file.
67
68Load build-abcl.lisp:
69
70    (load "build-abcl.lisp")
71
72Then do:
73
74    (build-abcl:build-abcl :clean t :full t)
75
76Wait for the build to finish and exit the host Lisp.
77
78Use abcl.bat on Windows or ./abcl on Unix to start ABCL.
79Note: abcl.bat and abcl contain absolute paths, so you'll need
80to edit them if you move things around after the build.
81
82In case of failure in the javac stage, you might try this:
83
84    (build-abcl:build-abcl :clean t :full t :batch nil)
85
86This invokes javac separately for each .java file, which avoids running
87into limitations on command line length (but is a lot slower).
88
89
90II. Ant-based build
91-------------------
92
93With Ant in your path, executing
94
95    ant -find build.xml abcl.wrapper
96
97from the directory containing this README file will create an
98executable wrapper ('abcl' under UNIX, 'abcl.bat' under Windows).
99Use this wrapper to start the ABCL Java program.
100
101
102III. Netbeans-based build
103-------------------------
104
105One should be able to open the project as a project in Netbeans 6.x.
106
107
108BUGS
109====
110
111A lot of (renewed) energy has been spent to make ABCL a compliant and
112practically useable Common Lisp implementation.  Because of this, ABCL
1130.0.13 now fails only 50 out of 21702 tests in the ANSI CL test suite.
114Next to that, the fail count of the Maxima test suite has been reduced
115from over 1400 in 0.0.10 to little more than 600 in 0.0.11, to xxx in
1160.13.
117
118ABCL's CLOS does not handle on-the-fly redefinition of classes
119correctly, and in any event is intolerably slow. There is no support
120for the long form of DEFINE-METHOD-COMBINATION, and certain other
121required CLOS features are also missing. Enough CLOS is there to run
122ASDF and CL-PPCRE, if you're in no hurry.
123
124There is no MOP worth mentioning.
125
126Since this is a early public release, there might be build
127problems as well as runtime bugs.
128
129Please report problems to the j-devel mailing list:
130
131    armedbear-j-devel@lists.sourceforge.net
132
133Have fun!
134
135On behalf of all ABCL development team and contributors,
136Erik Huelsmann
137Feburary 21, 2009
Note: See TracBrowser for help on using the repository browser.