* GNUmakefile.in (short-examples):

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

diff --git a/Documentation/topdocs/INSTALL.texi b/Documentation/topdocs/INSTALL.texi
index 1130e259d38fb41bf5895dc1764a2c004b188d68..df2bc044d089d335ab5f700c8c2e101d272e76e3 100644 (file)
--- a/Documentation/topdocs/INSTALL.texi
+++ b/Documentation/topdocs/INSTALL.texi
@@ -15,10 +15,10 @@
 @chapter INSTALL - compiling and installing GNU LilyPond
 
 
-This document describes how to build LilyPond on Unix platforms.  It is
-also known to run and compile on Windows NT/95/98 as well.  More
-information on this topic can be found at the
-@uref{http://www.lilypond.org/gnu-windows/, LilyPond on Windows page}.
+This document describes how to build LilyPond on Unix platforms.  It
+is also known to run and compile on Windows NT/95/98/ME/XP as well.
+More information on this topic can be found at the
+@uref{http://www.lilypond.org/cygwin/, LilyPond on Windows page}.
 
 
 @html
@@ -28,9 +28,9 @@ information on this topic can be found at the
 @section Downloading
 
 Even numbered versions are `stable'. The webpages for the stable version
-(1.2) reside @uref{http://www.gnu.org/software/lilypond, on the GNU
+(1.4) reside @uref{http://www.gnu.org/software/lilypond, on the GNU
 servers}. Big enhancements go into the latest odd numbered version
-(1.3), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
+(1.5), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
 site}.
 
 @subsection Source code
@@ -48,6 +48,7 @@ If you want to compile LilyPond from source, download here:
 @uref{http://www.lilypond.org/ftp/} by HTTP.
 @end itemize
 
+
 Of course, if your platform supports LilyPond, such as Debian GNU/Linux,
 FreeBSD, OpenBSD or NetBSD, you're encouraged to use the native build
 from source drill.
@@ -55,6 +56,20 @@ from source drill.
 For Red Hat Linux and SuSE Linux, @file{.spec} files are included in the
 tarball; see instructions below.
 
+
+@subsubsection Anonymous CVS access
+
+Short version:
+
+@quotation
+@example
+cvs -d :pserver:anoncvs@@lilypond.org:/home/lilypond login
+cvs -d :pserver:anoncvs@@lilypond.org:/home/lilypond co -P lilypond
+@end example
+@end quotation
+
+See @uref{http://lilypond.org/wiki/?CVS} for more information.
+
 @html
 <a name="download-binaries">
 @end html
@@ -117,8 +132,12 @@ on the FTP site.
 You need the following packages to compile Lilypond.
 
 @itemize
-@item A reasonably new version of the GNU C++ compiler:  EGCS 1.1, GCC 2.95.2 or
-newer. Check out @uref{ftp://ftp.gnu.org/gnu/gcc/, the gcc site}.
+@item The GNU c++ compiler (version 2.95.2 or newer).
+EGCS 1.1 may work, but is no longer supported.
+Check out @uref{ftp://ftp.gnu.org/gnu/gcc/, the gcc site}.
+
+WARNING: if you choose to upgrade to GCC 3.x, enquire if your
+distribution supports g++ 3.x and flex.
 
 @item Python (version 1.5 or newer).
 Check out @uref{http://www.python.org, the python website}.
@@ -135,6 +154,11 @@ make FTP directory}.
 @item Flex (version 2.5.4a or newer). 
 Check out @uref{http://www.gnu.org/software/flex/,the Flex webpage}.
 
+WARNING: plain Flex 2.5.4(a) generates invalid C++ code.  GCC 3.x
+chokes on this.  If you wish to use GCC 3.x, make sure that your
+distribution supports g++ 3.x and flex.  For a workaround, see
+lexer-gcc-3.0 below.
+
 @item Bison (version 1.25 or newer).
 Check out @uref{http://www.gnu.org/software/bison/,the bison  webpage}
 
@@ -168,9 +192,11 @@ UNIX), you can compile LilyPond without kpathsea support.  In that case,
 you'll probably have to indicate where @TeX{}'s tfm files live.  Invoke
 configure something like:
 
+@quotation
 @example
 ./configure --without-kpathsea --enable-tfm-path=/usr/share/texmf/fonts/tfm/public/cm/:/usr/share/texmf/fonts/tfm/ams/symbols
 @end example
+@end quotation
 
 @end itemize
 
@@ -182,7 +208,7 @@ following software
 @itemize @bullet
 @item @TeX{}.
 @item Xdvi and Ghostscript
-@item GUILE 1.3.4, or newer.  Check out
+@item GUILE 1.4, or newer.  Check out
 @uref{http://www.gnu.org/software/guile.html,the GUILE webpage}
 @end itemize
 
@@ -255,7 +281,9 @@ If you want to build multiple versions of LilyPond with different
 configuration settings, you can use the @code{--enable-config=CONF}
 option of configure.  You should use @samp{make conf=CONF} to generate
 the output in @file{out-CONF}.  Example: suppose I want to build with
-and without profiling.  Then I'd use the following for the normal build,
+and without profiling.  Then I'd use the following for the normal
+build,
+@c prefix=~ ?
 @example 
 
       ./configure --prefix=~ --enable-checking
@@ -309,7 +337,9 @@ file.
 @subsection Red Hat Linux
 
 Red Hat 7.x i386 RPMS are available from
-@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
+@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.  For running on
+a Red Hat system you need these packages: guile, tetex, tetex-latex,
+tetex-dvips, libstdc++, python, ghostscript.
 
 You can also compile them yourself.  A spec file is in
 @file{make/out/lilypond.redhat.spec}. This file is distributed along
@@ -322,9 +352,6 @@ with the sources.  You can make the rpm by issuing
 
 @end example 
 
-For running on a Red Hat system you need these packages: guile, tetex,
-tetex-latex, tetex-dvips, libstdc++, python, ghostscript.
-
 For compilation on a Red Hat system you need these packages, in
 addition to the those needed for running: glibc-devel, gcc-c++,
 libstdc++-devel, guile-devel, flex, bison, texinfo, groff, pktrace,
@@ -350,7 +377,7 @@ You can also compile a RPM for SUSE yourself.  A spec file is in
 the Red Hat RPM.
 
 You must have the following packages: guile tcsh tetex te_latex te_kpath
-te_mpost libpng python gpp libgpp gettext autoconf netpbm libnetpb
+te_mpost libpng python gpp libgpp gettext autoconf253 netpbm libnetpb
 gs_serv gs_lib gs_fonts guile
 
 @subsection Slackware