+2002-09-26 Han-Wen Nienhuys <hanwen@cs.uu.nl>
+
+ * Documentation/topdocs/INSTALL.texi (Top): recommend binary
+ packages.
+
+ * Documentation/topdocs/README.texi (Top): building documentation
+ (not website.)
+
2002-09-26 Jan Nieuwenhuizen <janneke@gnu.org>
* Documentation/user/refman.itely:
(1.5), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
site}.
+Building LilyPond is an involved process. We advise to use binary
+packages if these are available for your platform.
+
@subsection Source code
-If you want to compile LilyPond from source, download here:
+ If you want to compile LilyPond from source, download here:
@itemize @bullet
@item Download development releases from
@c Hmm, these won't show up in lilypond.org/stats
For Red Hat Linux and SuSE Linux, @file{.spec} files are included in the
tarball; see instructions below.
-
-
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.
LilyPond is a big and slow program. A fast CPU and plenty of RAM is
recommended for comfortable use.
-@subsection Building website
+@subsection Building documentation
-The documentation comes in the form of a website. You can view this
-website on the internet, but you can also build it locally. This process
-requires a successful compile of lilypond. The website is built
-by issuing
+You can view the documentation online at
+@uref{http://www.lilypond.org/stable/Documentation/out-www/}, but you
+can also build it locally. This process requires a successful compile of
+lilypond. The documentation is built by issuing
@example
make web-doc