Add support for QUIET_BUILD make variable

[lilypond.git] / Documentation / user / install.itely

diff --git a/Documentation/user/install.itely b/Documentation/user/install.itely
index a88a14212bf7fbb8208b4450beb50c26bac15764..78079e595b61705a4e125e38b4b10a7ea504579e 100644 (file)
--- a/Documentation/user/install.itely
+++ b/Documentation/user/install.itely
@@ -14,13 +14,6 @@
 @chapter Install
 @end ifclear
 
-@c  I don't know what this comment does.  Remove?  -gp
-@ignore
-@h tml
-<a name="download-source">
-@e nd html
-@end ignore
-
 There are two sets of releases for LilyPond: stable releases, and
 unstable development releases.  Stable versions have an even-numbered
 @q{minor} version number (i.e. 2.8, 2.10, 2.12, etc).  Development
@@ -39,7 +32,7 @@ recommend using the precompiled binaries.
 @node Precompiled binaries
 @section Precompiled binaries
 
-@subsection Downloading
+@unnumberedsubsec Downloading
 
 Check out @uref{http://lilypond.org/web/install/} for up to date
 information on binary packages for your platform.  If your operating
@@ -122,6 +115,9 @@ FOO-devel, libFOO-dev or FOO-dev package too.
 
 @item @uref{http://fontforge.sf.net/,FontForge} 20060125 or newer.
 
+@item MetaFont (mf-nowin, mf, mfw or mfont binaries), usually packaged with 
+a @LaTeX{} distribution like tetex or texlive.
+
 @item @uref{http://www.lcdf.org/~eddietwo/type/#t1utils,t1utils}
 (version 1.33 or newer recommended).
 
@@ -258,6 +254,14 @@ mkdir lily-build && cd lily-build
 
 @end example
 
+
+@unnumberedsubsubsec Useful @command{make} variables
+
+If a less verbose build output if desired, the variable
+@code{QUIET_BUILD} may be set to @code{1} on @command{make} command
+line, or in @file{local.make} at top of the build tree.
+
+
 @node Building documentation
 @subsection Building documentation
 
@@ -323,8 +327,22 @@ documentation maintenance are available from @file{Documentation/};
 for more information, see @file{Documentation/user/README.txt} and
 @file{Documentation/TRANSLATION}.
 
+The makefile variable @code{QUIET_BUILD} may be set to @code{1} for a
+less verbose build output, just like for building the programs.
+
 @knownissues
 
+@code{-j} command-line option of @command{make} is unsupported for
+building the documentation.  As the most time consuming task is
+running LilyPond to build images of music, the makefile variable
+@code{CPU_COUNT} may be set in @file{local.make} or on the command line
+to the number of @code{.ly} files that LilyPond should process
+simultaneously, e.g. on a bi-processor or dual core machine
+
+@example
+make CPU_COUNT=2 web
+@end example
+
 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