Emphasized the requirement for S48 0.53 and made some additions.
This commit is contained in:
parent
cba6e396b6
commit
7f8dc7f722
21
CVS_README
21
CVS_README
|
@ -14,18 +14,18 @@ repository, so anything may happen during the build process. The scsh
|
||||||
team does in general *not* provide support for code obtained from the
|
team does in general *not* provide support for code obtained from the
|
||||||
CVS repository.
|
CVS repository.
|
||||||
|
|
||||||
During the build process a number of auto generated files not included
|
During the build process a number of auto-generated files not included
|
||||||
in the CVS repository are built. It is highly recommended to follow
|
in the CVS repository are built. It is highly recommended to follow
|
||||||
these instructions carefully as otherwise incompatible versions of
|
these instructions carefully as otherwise incompatible versions of
|
||||||
generated files may result.
|
generated files may result.
|
||||||
|
|
||||||
To build Scsh, proceed as follows:
|
To build Scsh, proceed as follows:
|
||||||
|
|
||||||
1.) You must have a working version of Scheme 48, version 0.53. If you
|
1.) You must have a working version of Scheme 48, version 0.53. Nothing
|
||||||
don't have, get it from http://www.s48.org/0.53/scheme48-0.53.tgz
|
older, nothing newer. Just 0.53. If you don't have, get it from
|
||||||
and install Scheme 48. Change to value of the variable
|
http://www.s48.org/0.53/scheme48-0.53.tgz and install Scheme
|
||||||
BUILD_RUNNABLE in Makefile.in so that it will point to the Scheme
|
48. Change to value of the variable BUILD_RUNNABLE in Makefile.in
|
||||||
48 executable.
|
so that it will point to the Scheme 48 executable.
|
||||||
|
|
||||||
2.) "cd" into the directory which contains the source code (normally
|
2.) "cd" into the directory which contains the source code (normally
|
||||||
scsh-0.6) and run the script autogen.sh:
|
scsh-0.6) and run the script autogen.sh:
|
||||||
|
@ -50,7 +50,7 @@ To build Scsh, proceed as follows:
|
||||||
If anything fails here, fix the problem and/or contact the authors.
|
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
|
5.) You should have a runnable version of the system that can be
|
||||||
started in the build directory like this:
|
started in the main directory like this:
|
||||||
|
|
||||||
./go
|
./go
|
||||||
|
|
||||||
|
@ -61,6 +61,13 @@ To build Scsh, proceed as follows:
|
||||||
Note that it is not recommended to have a CVS version of Scsh for
|
Note that it is not recommended to have a CVS version of Scsh for
|
||||||
daily use.
|
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
|
You should repeat the whole build process whenever there are changes
|
||||||
to files in the directories scheme/vm, scheme/rts or
|
to files in the directories scheme/vm, scheme/rts or
|
||||||
scheme/bcomp. Watch the run of cvs update carefully and/or subscribe
|
scheme/bcomp. Watch the run of cvs update carefully and/or subscribe
|
||||||
|
|
Loading…
Reference in New Issue