From 7f8dc7f72218fbbda9779336bfa084afad549238 Mon Sep 17 00:00:00 2001 From: mainzelm Date: Thu, 8 Nov 2001 08:29:21 +0000 Subject: [PATCH] Emphasized the requirement for S48 0.53 and made some additions. --- CVS_README | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/CVS_README b/CVS_README index 26201cc..335b8fd 100644 --- a/CVS_README +++ b/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 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 these instructions carefully as otherwise incompatible versions of generated files may result. To build Scsh, proceed as follows: -1.) You must have a working version of Scheme 48, version 0.53. If you - don't have, get it from http://www.s48.org/0.53/scheme48-0.53.tgz - and install Scheme 48. Change to value of the variable - BUILD_RUNNABLE in Makefile.in so that it will point to the Scheme - 48 executable. +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 + 48. Change to value of the variable BUILD_RUNNABLE in Makefile.in + 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: @@ -50,7 +50,7 @@ To build Scsh, proceed as follows: 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 build directory like this: + started in the main directory like this: ./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 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