In addition to the packages needed for running LilyPond (see below), you
need the following extra packages for building.
+Below is a full list of packages needed to build LilyPond. However, for
+most common distributions there is an easy way of installing most all
+build dependencies in one go
+
+@multitable @columnfractions .5 .5
+@headitem Distribution
+@tab Command
+
+@item Debian, Ubuntu
+@tab @code{sudo apt-get build-dep lilypond}
+
+@item Fedora, RHEL
+@tab @code{sudo yum-builddep lilypond}
+
+@item openSUSE, SLED
+@c sorry for the idiosyncratic command, I really asked and argued
+@c for "zypper build-dep" :-(
+@tab @code{sudo zypper --build-deps-only source-install lilypond}
+
+@end multitable
+
When installing a binary package FOO, you may need to install the
FOO-devel, libFOO-dev or FOO-dev package too.
The documentation is built by issuing
@example
-make web
+make doc
@end example
After compilation, the HTML documentation tree is available in
standard documentation path by issuing
@example
-make web-install
+make install-doc
@end example
@noindent
Separate installation of this documentation is done by issuing
@example
-make info-install
+make install-info
@end example
@noindent
-Note that to get the images in Info documentation, @code{web-install}
+Note that to get the images in Info documentation, @code{install-doc}
target creates symbolic links to HTML and PDF installed documentation
tree in @file{@var{prefix}/share/info}, in order to save disk space,
-whereas @code{info-install} copies images in
+whereas @code{install-info} copies images in
@file{@var{prefix}/share/info} subdirectories.
It is possible to build a documentation tree in
selection; this can be achieved by issuing
@example
-make WEB_TARGETS=online web
+make WEB_TARGETS=online doc
@end example
@noindent
and both @q{offline} and @q{online} targets can be generated by issuing
@example
-make WEB_TARGETS="offline online" web
+make WEB_TARGETS="offline online" doc
@end example
Several targets are available to clean the documentation build and
a bi-processor or dual core machine
@example
-make -j3 CPU_COUNT=3 web
+make -j3 CPU_COUNT=3 doc
@end example
@noindent
If source files have changed since last documentation build, output
files that need to be rebuilt are normally rebuilt, even if you do not
-run @code{make web-clean} first. However, building dependencies in the
+run @code{make doc-clean} first. However, building dependencies in the
documentation are so complex that rebuilding of some targets may not
be triggered as they should be; a workaround is to force rebuilding
by touching appropriate files, e.g.
./autogen.sh # ignore any warning messages
cp GNUmakefile.in GNUmakefile
make -C python
-nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web
+nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond doc
@end example
Please note that this may break sometimes -- for example, if a new
You may build the manual without building all the @file{input/*}
stuff: change directory, for example to @file{Documentation/user},
-issue @code{make web}, which will build documentation in a
+issue @code{make doc}, which will build documentation in a
subdirectory @file{out-www} from the source files in current
directory. In this case, if you also want to browse the documentation
in its post-processed form, change back to top directory and issue