+ Overview of compiling
+ Requirements
+ Requirements for running LilyPond
+ Requirements for compiling LilyPond
+ Requirements for building documentation
+ Getting the source code
+ Configuring `make'
+ Running `./autogen.sh'
+ Running `../configure'
+ Configuration options
+ Checking build dependencies
+ Configuring target directories
+ Compiling LilyPond
+ Using `make'
+ Saving time with the `-j' option
+ Compiling for multiple platforms
+ Useful `make' variables
+ Post-compilation options
+ Installing LilyPond from a local build
+ Generating documentation
+ Documentation editor's edit/compile cycle
+ Building documentation
+ Saving time with `CPU_COUNT'
+ AJAX search
+ Installing documentation
+ Building documentation without compiling
+ Testing LilyPond binary
+ Problems
+ Bison 1.875
+ Compiling on MacOS X
+ Solaris
+ FreeBSD
+ International fonts
+ Using lilypond python libraries
+ Concurrent stable and development versions
+ Build system
+
+
+Overview of compiling
+=====================
+
+Compiling LilyPond from source is an involved process, and is only
+recommended for developers and packagers. Typical program users are
+instead encouraged to obtain the program from a package manager (on
+Unix) or by downloading a precompiled binary configured for a specific
+operating system. Pre-compiled binaries are available on the *note
+Download: (lilypond-web)Download. page.
+
+ Compiling LilyPond from source is necessary if you want to build,
+install, or test your own version of the program.
+
+ A successful compile can also be used to generate and install the
+documentation, incorporating any changes you may have made. However, a
+successful compile is not a requirement for generating the
+documentation. The documentation can be built using a Git repository
+in conjunction with a locally installed copy of the program. For more
+information, see *note Building documentation without compiling::.
+
+ Attempts to compile LilyPond natively on Windows have been
+unsuccessful, though a workaround is available (see *note Lilydev:
+(lilypond-contributor)Lilydev.).
+
+Requirements
+============
+
+Requirements for running LilyPond
+---------------------------------
+
+Running LilyPond requires proper installation of the following software:
+
+ * DejaVu fonts (http://www.dejavu-fonts.org/) (normally installed by
+ default)
+
+ * FontConfig (http://www.fontconfig.org/) (2.4.0 or newer)
+
+ * Freetype (http://www.freetype.org/) (2.1.10 or newer)
+
+ * Ghostscript (http://www.ghostscript.com) (8.60 or newer)
+
+ * Guile (http://www.gnu.org/software/guile/guile.html) (1.8.2 or
+ newer)
+
+ * Pango (http://www.pango.org/) (1.12 or newer)
+
+ * Python (http://www.python.org) (2.4 or newer)
+
+ International fonts are required to create music with international
+text or lyrics.
+
+Requirements for compiling LilyPond
+-----------------------------------
+
+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:
+
+Distribution Command
+--------------------------------------------------------------------------
+Debian, Ubuntu `sudo apt-get build-dep lilypond'
+Fedora, RHEL `sudo yum-builddep lilypond'
+openSUSE, SLED `sudo zypper --build-deps-only
+ source-install lilypond'
+
+ * Everything listed in *note Requirements for running LilyPond::
+
+ * Development packages for the above items (which should include
+ header files and libraries).
+
+ Red Hat Fedora:
+
+ guile-devel-VERSION
+ fontconfig-devel-VERSION
+ freetype-devel-VERSION
+ pango-devel-VERSION
+ python-devel-VERSION
+
+ Debian GNU/Linux:
+
+ guile-VERSION-dev
+ libfontconfig1-dev
+ libfreetype6-dev
+ libpango1.0-dev
+ pythonVERSION-dev
+
+ * Flex (http://flex.sourceforge.net/)
+
+ * FontForge (http://fontforge.sf.net/) (20060125 or newer; 20100501
+ or newer is recommended; must be compiled with `--enable-double'.
+ Failure to do so can lead to poor intersection calculations and
+ poorly-rendered glyphs.)
+
+ * GNU Bison (http://www.gnu.org/software/bison/)
+
+ * GNU Compiler Collection (http://gcc.gnu.org/) (3.4 or newer, 4.X
+ recommended)
+
+ * GNU gettext (http://www.gnu.org/software/gettext/gettext.html)
+ (0.17 or newer)
+
+ * GNU Make (http://www.gnu.org/software/make/) (3.78 or newer)
+
+ * MetaFont (http://metafont.tutorial.free.fr/) (mf-nowin, mf, mfw or
+ mfont binaries), usually packaged with TeX
+ (http://www.latex-project.org/ftp.html).
+
+ * MetaPost (http://cm.bell-labs.com/who/hobby/MetaPost.html) (mpost
+ binary), usually packaged with TeX
+ (http://www.latex-project.org/ftp.html).
+
+ * Perl (http://www.perl.org/)
+
+ * Texinfo (http://www.gnu.org/software/texinfo/) (4.11 or newer)
+
+ * Type 1 utilities (http://www.lcdf.org/~eddietwo/type/#t1utils)
+ (1.33 or newer recommended)
+
+Requirements for building documentation
+---------------------------------------
+
+You can view the documentation online at
+`http://www.lilypond.org/doc/', but you can also build it locally.
+This process requires some additional tools and packages:
+
+ * Everything listed in *note Requirements for compiling LilyPond::
+
+ * ImageMagick (http://www.imagemagick.org/)
+
+ * Netpbm (http://netpbm.sourceforge.net/)