1.2.2 Requirements

Compilation

In addition to the packages needed for running Lilypond (see below), you need the following extra packages for building.

When installing a binary package FOO, you may need to install the FOO-devel, libFOO-dev or FOO-dev package too.

• FontForge 20060125 or newer.
• New Century Schoolbook fonts, as PFB files. These are shipped with X11 and Ghostscript, and are named c059033l.pfb c059036l.pfb, c059013l.pfb and c059016l.pfb
• mftrace (1.1.19 or newer); you may need to install some additional packages to get mftrace to work.
• GUILE (version 1.8.2 or newer). If you are installing binary packages, you may need to install guile-devel or guile-dev or libguile-dev too.
• Texinfo (version 4.8 or newer).
• The GNU c++ compiler (version 4.x or newer).
• Python (version 2.4 or newer)
• GNU Make (version 3.78 or newer).
• gettext.
• Flex
• Perl
• GNU Bison
• All packages required for running, including development packages with header files and libraries.

Running requirements

Running LilyPond requires proper installation of the following software

• Freetype (version 2.1.10 or newer).
• FontConfig (version 2.2).
• Pango (version 1.12 or newer).
• GUILE (version 1.8.2 or newer), or patch 1.8.1 with http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch.
• Python (version 2.4 or newer).
• Ghostscript (version 8.15 or newer. 8.50 recommended)
• Dejaview. (This is normally installed by default)

International fonts are required to create music with international text or lyrics.

Building documentation

You can view the documentation online at http://lilypond.org/doc/, but you can also build it locally. This process requires a successful compile of lilypond. The documentation is built by issuing

     make web

Building the website requires some additional tools and packages

• The netpbm utilities
• ImageMagick
• International fonts (see input/regression/utf-8.ly for hints about which font packages are necessary for your platform)
• Ghostscript, 8.50 with the patch from http://bugs.ghostscript.com/show_bug.cgi?id=688154 and the patch from http://bugs.ghostscript.com/show_bug.cgi?id=688017.

The HTML files can be installed into the standard documentation path by issuing

     make out=www web-install