2003-05-01 06:21:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Welcome to the Scsh CVS Repository !!!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This file contains some instructions about how to build Scsh after you
|
|
|
|
freshly checked out the "scsh-0.6" module. These instructions do *not*
|
|
|
|
apply to the module named "scsh" or the Scsh distribution itself.
|
|
|
|
|
|
|
|
There is currently no scheme to tag working snapshots of the
|
|
|
|
repository, so anything may happen during the build process. The scsh
|
|
|
|
team does in general *not* provide support for code obtained from the
|
|
|
|
CVS repository.
|
|
|
|
|
|
|
|
During the build process a number of auto-generated files not included
|
|
|
|
in the CVS repository are built. It is highly recommended to follow
|
|
|
|
these instructions carefully as otherwise incompatible versions of
|
|
|
|
generated files may result. Note that you need GNU make for this
|
|
|
|
process.
|
|
|
|
|
|
|
|
To build Scsh, proceed as follows:
|
|
|
|
|
|
|
|
1.) You must have a working version of Scheme 48, version 0.53. Nothing
|
|
|
|
older, nothing newer. Just 0.53. If you don't have, get it from
|
|
|
|
http://www.s48.org/0.53/scheme48-0.53.tgz and install Scheme
|
2006-03-08 06:48:59 -05:00
|
|
|
48. Change the value of the variable BUILD_RUNNABLE in Makefile.in
|
2003-05-01 06:21:33 -04:00
|
|
|
so that it will point to the Scheme 48 executable.
|
|
|
|
|
|
|
|
2.) "cd" into the directory which contains the source code (normally
|
|
|
|
scsh-0.6) and run the script autogen.sh:
|
|
|
|
|
|
|
|
./autogen.sh
|
|
|
|
|
|
|
|
This will take several minutes and generate the source code for
|
|
|
|
the virtual machine and two images the Makefile relies
|
|
|
|
on. Furthermore the configure file will be generated. This script
|
|
|
|
calls autoheader and autoconf from the GNU Autoconf package. You
|
|
|
|
will need a recent version of Autoconf. Version 2.52 is okay,
|
|
|
|
version 2.13 is too old.
|
|
|
|
|
|
|
|
3.) Configure the system:
|
|
|
|
|
|
|
|
./configure
|
|
|
|
|
|
|
|
You presumably want to add the --prefix flag here to determine the
|
|
|
|
installation directory. This will generate the Makefile.
|
|
|
|
|
|
|
|
4.) Build the system:
|
|
|
|
|
|
|
|
make
|
|
|
|
|
|
|
|
If anything fails here, fix the problem and/or contact the authors.
|
|
|
|
|
|
|
|
5.) You should have a runnable version of the system that can be
|
|
|
|
started in the main directory like this:
|
|
|
|
|
|
|
|
./go
|
|
|
|
|
|
|
|
6.) To install Scsh, type:
|
|
|
|
|
|
|
|
make install
|
|
|
|
|
|
|
|
Note that it is not recommended to have a CVS version of Scsh for
|
|
|
|
daily use.
|
|
|
|
|
|
|
|
7.) If you intend to build on a different platform later, do a
|
|
|
|
|
|
|
|
make distclean
|
|
|
|
|
|
|
|
and restart at step 3.
|
|
|
|
|
|
|
|
|
|
|
|
You should repeat the whole build process whenever there are changes
|
|
|
|
to files in the directories scheme/vm, scheme/rts or
|
|
|
|
scheme/bcomp. Watch the run of cvs update carefully and/or subscribe
|
|
|
|
to the list scsh-checkins@lists.sourceforge.net.
|
|
|
|
|
|
|
|
|
|
|
|
Enjoy!!!
|
|
|
|
|
|
|
|
|
|
|
|
The Scsh developers
|
|
|
|
|