| 1 | GENERAL INFORMATION |
|---|
| 2 | ------------------- |
|---|
| 3 | |
|---|
| 4 | Armed Bear Common Lisp is an implementation of ANSI Common Lisp that runs in a |
|---|
| 5 | Java virtual machine. |
|---|
| 6 | |
|---|
| 7 | |
|---|
| 8 | LICENSE |
|---|
| 9 | ------- |
|---|
| 10 | |
|---|
| 11 | Armed Bear Common Lisp is distributed under the GNU General Public License |
|---|
| 12 | (with a special exception described below). |
|---|
| 13 | |
|---|
| 14 | A copy of GNU General Public License (GPL) is included in this distribution, in |
|---|
| 15 | the file COPYING. |
|---|
| 16 | |
|---|
| 17 | Linking this software statically or dynamically with other modules is making a |
|---|
| 18 | combined work based on this software. Thus, the terms and conditions of the GNU |
|---|
| 19 | General Public License cover the whole combination. |
|---|
| 20 | |
|---|
| 21 | As a special exception, the copyright holders of this software give you |
|---|
| 22 | permission to link this software with independent modules to produce an |
|---|
| 23 | executable, regardless of the license terms of these independent modules, and |
|---|
| 24 | to copy and distribute the resulting executable under terms of your choice, |
|---|
| 25 | provided that you also meet, for each linked independent module, the terms and |
|---|
| 26 | conditions of the license of that module. An independent module is a module |
|---|
| 27 | which is not derived from or based on this software. If you modify this |
|---|
| 28 | software, you may extend this exception to your version of the software, but |
|---|
| 29 | you are not obligated to do so. If you do not wish to do so, delete this |
|---|
| 30 | exception statement from your version. |
|---|
| 31 | |
|---|
| 32 | |
|---|
| 33 | INSTALLATION |
|---|
| 34 | ------------ |
|---|
| 35 | |
|---|
| 36 | To build ABCL, you'll need a 1.4 or 1.5 JDK and a supported Common Lisp |
|---|
| 37 | implementation (SBCL, CMUCL, Allegro, or LispWorks). |
|---|
| 38 | |
|---|
| 39 | Edit the file customizations.lisp, in this directory, to suit your situation. |
|---|
| 40 | |
|---|
| 41 | Start up one of the supported Common Lisp implementations in the directory |
|---|
| 42 | containing this README file. |
|---|
| 43 | |
|---|
| 44 | Load build-abcl.lisp: |
|---|
| 45 | |
|---|
| 46 | (load "build-abcl.lisp") |
|---|
| 47 | |
|---|
| 48 | Then do: |
|---|
| 49 | |
|---|
| 50 | (build-abcl:build-abcl :clean t :full t) |
|---|
| 51 | |
|---|
| 52 | Wait for the build to finish and exit the host Lisp. |
|---|
| 53 | |
|---|
| 54 | Use abcl.bat on Windows or ./abcl on Unix to start ABCL. |
|---|
| 55 | |
|---|
| 56 | |
|---|
| 57 | BUGS |
|---|
| 58 | ---- |
|---|
| 59 | |
|---|
| 60 | ABCL is a very young implementation. The current version, 0.0.5, is the first |
|---|
| 61 | public release. You are certain to encounter bugs. |
|---|
| 62 | |
|---|
| 63 | ABCL 0.0.5 fails 79 out of 20817 test in the GCL ANSI test suite. |
|---|
| 64 | |
|---|
| 65 | ABCL's CLOS does not handle on-the-fly redefinition of classes correctly, and |
|---|
| 66 | in any event is intolerably slow. There is no support for the long form of |
|---|
| 67 | DEFINE-METHOD-COMBINATION, and certain other required CLOS features are also |
|---|
| 68 | missing. Enough CLOS is there to run ASDF and CL-PPCRE, if you're in no hurry. |
|---|
| 69 | |
|---|
| 70 | There's no MOP worth mentioning. |
|---|
| 71 | |
|---|
| 72 | Since this is the first public release, there are likely to be build problems |
|---|
| 73 | as well as runtime bugs. I don't have a Mac, so I've done no testing at all on |
|---|
| 74 | OS X. |
|---|
| 75 | |
|---|
| 76 | Please report problems to the j-devel mailing list: |
|---|
| 77 | |
|---|
| 78 | armedbear-j-devel@lists.sourceforge.net |
|---|
| 79 | |
|---|
| 80 | Have fun! |
|---|
| 81 | |
|---|
| 82 | Peter Graves |
|---|
| 83 | May 31 2005 |
|---|
