release: 1.1.1

[lilypond.git] / Documentation / topdocs / INSTALL.yo

diff --git a/Documentation/topdocs/INSTALL.yo b/Documentation/topdocs/INSTALL.yo
index 9a7251676467dcd5ec66128b3b5fa381940c2966..54147f74e19a612023899c00aee23dc20c92d5ba 100644 (file)
--- a/Documentation/topdocs/INSTALL.yo
+++ b/Documentation/topdocs/INSTALL.yo
@@ -4,13 +4,13 @@ sect(ABSTRACT)
 
 You do something which looks remotely like
 verb(
-       configure    # Check out the bin/set-lily.sh script
+       configure    # Check out the buildscripts/set-lily.sh script
        make
        make install
 )
 
 The detailed instructions follow here.  The
-file(bin/set-lily.sh) script sets some environment variables
+file(buildscripts/set-lily.sh) script sets some environment variables
 and symlinks, which comes in handly when you have to compile LilyPond
 very often.  It is aimed at people who run (or debug) LilyPond without 
 installing.
@@ -35,6 +35,8 @@ it() GNU C++ version 2.7 or newer (2.8 and egcs are also fine).
 it() Python 1.5 (Strictly speaking, you shouldn't need Python for 
    compiling and installing, but you'll need it to regenerate the font
    tables, e.g.). 
+
+it() GUILE 1.3 (no, GUILE 1.2 won't work)
 )
 
 sect(RUNNING)
@@ -60,8 +62,8 @@ export TEXINPUTS="/usr/local/share/lilypond/tex:"
 The empty path component
 represents TeX() and MetaFont's default search paths.  Scripts with
 the proper paths for the bourne and C-shell respectively are generated in
-file(bin/out/lilypond-profile) and
-file(bin/out/lilypond-login) during compilation.
+file(buildscripts/out/lilypond-profile) and
+file(buildscripts/out/lilypond-login) during compilation.
 
 
 sect(RECOMMENDED)