+INSTALL - compiling and installing GNU LilyPond
+***********************************************
+Table of Contents
+*****************
+INSTALL - compiling and installing GNU LilyPond
+ Precompiled binaries
+ Downloading
+ Compiling from source
+ Downloading source code
+ Requirements
+ Compilation
+ Running requirements
+ Requirements for building documentation
+ Building LilyPond
+ Compiling
+ Compiling for multiple platforms
+ Compiling outside the source tree
+ Useful `make' variables
+ Building documentation
+ Commands for building documentation
+ Building documentation without compiling LilyPond
+ Testing LilyPond
+ Problems
+ Bison 1.875
+ Solaris
+ FreeBSD
+ International fonts
+There are two sets of releases for LilyPond: stable releases, and
+unstable development releases. Stable versions have an even-numbered
+`minor' version number (i.e. 2.8, 2.10, 2.12, etc). Development
+versions have an odd-numbered `minor' version number (i.e. 2.7, 2.9,
+2.11, etc).
+ Building LilyPond is a very involved process, so we *highly*
+recommend using the precompiled binaries.
+Precompiled binaries
+====================
+Downloading
+-----------
+Check out `http://lilypond.org/web/install/' for up to date information
+on binary packages for your platform. If your operating system is not
+covered on that general page, please see the complete list at
+`http://download.linuxaudio.org/lilypond/binaries/'
- INSTALL - compiling and installing GNU LilyPond
+ We currently create binaries for
- HWN & JCN
+ darwin-ppc - MacOS X powerpc
+ darwin-x86 - MacOS X intel
+ freebsd-64 - FreeBSD 6.x, x86_64
+ freebsd-x86 - FreeBSD 4.x, x86
+ linux-64 - Any GNU/Linux distribution, x86_64
+ linux-ppc - Any GNU/Linux distribution, powerpc
+ linux-x86 - Any GNU/Linux distribution, x86
+ mingw - Windows x86
-Contents
+Known issues and warnings
+.........................
- 1: ABSTRACT
-2: PREREQUISITES
-3: RUNNING
-4: RECOMMENDED
-5: WEBSITE
-6: CONFIGURING and COMPILING
-7: CONFIGURING FOR MULTIPLE PLATFORMS
-8: INSTALLING
-9: REDHAT LINUX
-10: DEBIAN GNU/LINUX
-11: WINDOWS NT/95
-12: AUTHORS
+If you have MacOS 10.3 or 10.4 and you would like to use Python scripts
+such as `convert-ly' and `lilypond-book', see *note Setup for MacOS X:
+(lilypond-program)Setup for MacOS X.
+Compiling from source
+=====================
-1: ABSTRACT
+Downloading source code
+-----------------------
+Download source
-You do something which looks remotely like
+ * tarballs from `http://lilypond.org/download/' by HTTP.
+ * tarballs from `http://download.linuxaudio.org/lilypond/' by HTTP.
+ * GIT from git.sv.gnu.org
+ (http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary)
+ git clone git://git.sv.gnu.org/lilypond.git
+ The repository does not contain generated files. To create
+ `configure', run
+ ./autogen.sh
- configure # Check out the buildscripts/set-lily.sh script
- make
- make install
+ For information on packaging, see `http://lilypond.org/devel'.
+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.
-The detailed instructions follow here. The build-
-scripts/set-lily.sh script sets some environment variables
-and symlinks, which comes in handly when you have to compile
-LilyPond very often. It is aimed at people who run (or
-debug) LilyPond without installing.
+ * FontForge (http://fontforge.sf.net/) 20060125 or newer.
+ * MetaFont (http://metafont.tutorial.free.fr/) (mf-nowin, mf, mfw or
+ mfont binaries) and MetaPost
+ (http://cm.bell-labs.com/who/hobby/MetaPost.html) (mpost binary),
+ usually packaged with a LaTeX distribution like tetex or texlive.
-2: PREREQUISITES
+ * t1utils (http://www.lcdf.org/~eddietwo/type/#t1utils) (version
+ 1.33 or newer recommended).
+ * 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'.
-For compilation you need:
+ * GUILE (http://www.gnu.org/software/guile/guile.html) (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 (ftp://ftp.gnu.org/gnu/texinfo/) (version 4.11 or newer).
-o A GNU system: GNU LilyPond is known to run on these GNU
- systems: Linux (PPC, intel), FreeBSD, AIX, NeXTStep,
- IRIX, Digital Unix and Solaris.
+ * The GNU c++ compiler (http://gcc.gnu.org/) (version 3.4 or newer.
+ 4.x is strongly recommended).
+ * Python (http://www.python.org) (version 2.4 or newer)
-o Lots of disk space: LilyPond takes between 50 and 100
- mb to compile if you use debugging information. If you
- are short on disk-space run configure with --disable-
- debugging.
+ * GNU Make (ftp://ftp.gnu.org/gnu/make/) (version 3.78 or newer).
- Although we recommend to use Unix, LilyPond is known to
- run on Windows NT/95/98 as well. See Section 11.
+ * gettext (http://www.gnu.org/software/gettext/gettext.html)
+ (version 0.17 or newer).
+ * Flex (http://www.gnu.org/software/flex/).
-o GNU C++ version 2.7 or newer (2.8 and egcs are also
- fine).
+ * Perl (http://www.perl.org/).
-o Python 1.5 (Strictly speaking, you shouldn't need
- Python for compiling and installing, but you'll need it
- to regenerate the font tables, e.g.).
+ * GNU Bison (http://www.gnu.org/software/bison/).
+ * All packages required for running, including development packages
+ with header files and libraries.
-o GUILE 1.3 (no, GUILE 1.2 won't work)
+Running requirements
+....................
-3: RUNNING
+Running LilyPond requires proper installation of the following software
+ * Freetype (http://www.freetype.org/) (version 2.1.10 or newer).
-GNU LilyPond does use a lot of resources. For operation you
-need the following:
+ * FontConfig (http://fontconfig.org/) (version 2.2 or newer).
+ * Pango (http://www.pango.org/) (version 1.12 or newer).
-o TeX
+ * GUILE (http://www.gnu.org/software/guile/guile.html) (version
+ 1.8.2 or newer), or patch 1.8.1 with
+ `http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch'.
-o A PostScript printer and/or viewer (such as
- Ghostscript) is strongly recommended. Xdvi will show
- all embedded PostScript too if you have Ghostscript
- installed.
+ * Python (http://www.python.org) (version 2.4 or newer).
-For running LilyPond successfully you have to help TeX and
-MetaFont find various files. The recommended way of doing
-so is adjusting the environment variables in the start-up
-scripts of your shell. An example is given here for the
-Bourne shell:
+ * Ghostscript (http://www.ghostscript.com) (version 8.15 or newer.
+ 8.60 recommended)
+ * Dejaview. (This is normally installed by default)
+ International fonts are required to create music with international
+text or lyrics.
+Requirements for building documentation
+.......................................
- export MFINPUTS="/usr/local/share/lilypond/mf:"
- export TEXINPUTS="/usr/local/share/lilypond/tex:"
+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, and some additional tools and packages:
+ * The netpbm utilities (http://netpbm.sourceforge.net/)
+ * ImageMagick
+ * International fonts (see input/regression/utf-8.ly for hints about
+ which font packages are necessary for your platform)
-The empty path component represents and MetaFont's default
-search paths. Scripts with the proper paths for the bourne
-and C-shell respectively are generated in build-
-scripts/out/lilypond-profile and buildscripts/out/lilypond-
-login during compilation.
+ * Ghostscript 8.60 or newer, or 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'.
+ * Texi2HTML (http://www.nongnu.org/texi2html/) 1.80 or newer
-4: RECOMMENDED
+ * rsync
+Building LilyPond
+-----------------
-Although not strictly necessary, these are recommended to
-have.
+Compiling
+.........
+To install GNU LilyPond, type
-o GNU make. Check out ftp://ftp.gnu.org or any mirror of
- this site.
+ gunzip -c lilypond-x.y.z | tar xf -
+ cd lilypond-x.y.z
+ ./configure # run with --help for applicable options
+ make
+ su -c 'make install'
+If you are not root, you should choose a `--prefix' argument that
+points into your home directory, e.g.
-o Flex (version 2.5.4 or newer). Check out
- ftp://ftp.gnu.org or any mirror of this site.
+ ./configure --prefix=$HOME/usr
-o Bison (version 1.25 or newer). Check out
- ftp://ftp.gnu.org or any mirror of this site.
+Compiling for multiple platforms
+................................
+If you want to build multiple versions of LilyPond with different
+configuration settings, you can use the `--enable-config=CONF' option
+of `configure'. You should use `make conf=CONF' to generate the output
+in `out-CONF'. For example, suppose you want to build with and without
+profiling, then use the following for the normal build
-o GUILE (version 1.2) Check out http://www.gnu.org/pro-
- grams/guile.html
+ ./configure --prefix=$HOME/usr/ --enable-checking
+ make
+ make install
+ and for the profiling version, specify a different configuration
-o Python (version 1.5 or newer). Check out
- ftp://ftp.python.org or ftp://ftp.cwi.nl/pub/python.
+ ./configure --prefix=$HOME/usr/ --enable-profiling --enable-config=prof --disable-checking
+ make conf=prof
+ make conf=prof install
+Compiling outside the source tree
+.................................
-o Yodl. All documentation will be in Yodl. (1.30.17)
- ftp://pcnov095.win.tue.nl/pub/yodl
- http://www.cs.uu.nl/~hanwen/yodl
+It is possible to compile LilyPond in a build tree different from the
+source tree, with `--srcdir' option of `configure':
-o Texinfo. (version 3.12 or newer)
+ mkdir lily-build && cd lily-build
+ SOURCEDIR/configure --srcdir=SOURCEDIR
+Useful `make' variables
+.......................
-o GNU find Check out ftp://ftp.gnu.org or any mirror of
- this site.
+If a less verbose build output if desired, the variable `QUIET_BUILD'
+may be set to `1' on `make' command line, or in `local.make' at top of
+the build tree.
+Building documentation
+----------------------
-o The geometry package for LaTeX is needed to use ly2dvi.
- Available at ftp://ftp.ctan.org/tex-
- archive/macros/latex/contrib/supported/geometry or at
- mirror site ftp://ftp.dante.de
+This requires a successful compile of LilyPond, or using an external
+LilyPond binary.
+Commands for building documentation
+...................................
-o A fast computer (a full page of music typically takes 1
- minute on my 486/133, using the --enable-checking com-
- pile. It's lot slower than most MusiXTeX preprocessors)
+The documentation is built by issuing
+ make doc
-5: WEBSITE
+ After compilation, the HTML documentation tree is available in
+`out-www/offline-root/', and can be browsed locally.
+ The HTML, PDF and if available Info files can be installed into the
+standard documentation path by issuing
-If you want to auto-generate Lily's website, you'll need
-some additional conversion tools.
+ make install-doc
+This also installs Info documentation with images if the installation
+prefix is properly set; otherwise, instructions to complete proper
+installation of Info documentation are printed on standard output.
-o xpmtoppm (from the Portable Bitmap Utilities) (For Red-
- Hat Linux users: it is included within the package
- libgr-progs).
+ Compilation of documentation in Info format with images can be done
+separately by issuing
-o Bib2html http://pertsserver.cs.uiuc.edu/~hull/bib2html.
- Which, in turn depends on man2html for proper installa-
- tion. man2html can be had from http://askdon-
- ald.ask.uni-karlsruhe.de/hppd/hpux/Network-
- ing/WWW/Man2html-1.05.
+ make info
- TeTeX users should not forget to rerun texhash.
+Separate installation of this documentation is done by issuing
-Building the website requires pnmtopng. The version of pnm-
-topng that is distributed with RedHat 5.1 contains a bug
-(pnmtopng is dynamically linked to the wrong version of
-libpng). Recompile it from source, and make sure that the
-pnmtopng binary is linked statically to the libpng that is
+ make install-info
+Note that to get the images in Info documentation, `install-doc' target
+creates symbolic links to HTML and PDF installed documentation tree in
+`PREFIX/share/info', in order to save disk space, whereas
+`install-info' copies images in `PREFIX/share/info' subdirectories.
-included in libgr.
+ It is possible to build a documentation tree in
+`out-www/online-root/', with special processing, so it can be used on a
+website with content negotiation for automatic language selection; this
+can be achieved by issuing
+ make WEB_TARGETS=online doc
+and both `offline' and `online' targets can be generated by issuing
+ make WEB_TARGETS="offline online" doc
+ Several targets are available to clean the documentation build and
+help with maintaining documentation; an overview of these targets is
+available with
- tar xzf libgr-2.0.13.tar.gz
- make
- cd png
- rm libpng.so*
- make pnmtopng
+ make help
+from every directory in the build tree. Most targets for documentation
+maintenance are available from `Documentation/'; for more information,
+see the Contributors' Guide, section _Documentation work_.
+ The makefile variable `QUIET_BUILD' may be set to `1' for a less
+verbose build output, just like for building the programs.
-You can then install the new pnmtopng into /usr/local/bin/
+Known issues and warnings
+.........................
+The most time consuming task for building the documentation is running
+LilyPond to build images of music, and there cannot be several
+simultaneously running `lilypond-book' instances, so `-j' `make' option
+does not significantly speed up the build process. To help speed it
+up, the makefile variable CPU_COUNT may be set in `local.make' or on
+the command line to the number of `.ly' files that LilyPond should
+process simultaneously, e.g. on a bi-processor or dual core machine
-6: CONFIGURING and COMPILING
+ make -j3 CPU_COUNT=3 doc
+The recommended value of CPU_COUNT is one plus the number of cores or
+processors, but it is advisable to set it to a smaller value if your
+system has not enough RAM to run that many simultaneous LilyPond
+instances.
-to install GNU LilyPond, simply type:
+ 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 `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.
+ touch Documentation/user/*.itely
+ touch input/lsr/*.ly
+Building documentation without compiling LilyPond
+.................................................
+The documentation can be built locally without compiling LilyPond
+binary, if LilyPond is already installed on your system.
+ From a fresh Git checkout, do
- configure
- make
- make install
+ ./autogen.sh # ignore any warning messages
+ cp GNUmakefile.in GNUmakefile
+ make -C python
+ nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond doc
+ Please note that this may break sometimes - for example, if a new
+feature is added with a test file in input/regression, even the latest
+development release of LilyPond will fail to build the docs.
+ You may build the manual without building all the `input/*' stuff:
+change directory, for example to `Documentation/user', issue `make
+doc', which will build documentation in a subdirectory `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
+ make out=www WWW-post
-This will install a number of files, something close to:
+Known issues and warnings
+.........................
+You may also need to create a script for `pngtopnm' and `pnmtopng'. On
+GNU/Linux, I use this:
+export LD_LIBRARY_PATH=/usr/lib
+exec /usr/bin/pngtopnm "$@"
+ On MacOS X, I use this:
+export DYLD_LIBRARY_PATH=/sw/lib
+exec /sw/bin/pngtopnm "$@"
- /usr/local/man/man1/mi2mu.1
- /usr/local/man/man1/convert-mudela.1
- /usr/local/man/man1/mudela-book.1
- /usr/local/man/man1/lilypond.1
- /usr/local/bin/lilypond
- /usr/local/bin/mi2mu
- /usr/local/share/lilypond/*
- /usr/local/share/locale/{it,nl}/LC_MESSAGES/lilypond.mo
+Testing LilyPond
+----------------
+LilyPond comes with an extensive suite that exercises the entire
+program. This suite can be used to automatically check the impact of a
+change. This is done as follows
-The above assumes that you are root and have the GNU devel-
-opment tools, and your make is GNU make. If this is not the
-case, you can adjust your environment variables to your
-taste:
+ make test-baseline
+ _## apply your changes, compile_
+ make check
+ This will leave an HTML page `out/test-results/index.html'. This
+page shows all the important differences that your change introduced,
+whether in the layout, MIDI, performance or error reporting.
+ To rerun tests, use
+ make test-redo _## redo files differing from baseline_
+ make test-clean _## remove all test results_
+and then run `make check' again.
+ For tracking memory usage as part of this test, you will need GUILE
+CVS; especially the following patch:
+`http://lilypond.org/vc/gub.darcs/patches/guile-1.9-gcstats.patch'.
- export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR"
- configure
+ For checking the coverage of the test suite, do the following
+ ./scripts/auxiliar/build-coverage.sh
+ _# uncovered files, least covered first_
+ ./scripts/auxiliar/coverage.py --summary out-cov/*.cc
+ _# consecutive uncovered lines, longest first_
+ ./scripts/auxiliar/coverage.py --uncovered out-cov/*.cc
+Problems
+--------
+For help and questions use <lilypond-user@gnu.org>. Send bug reports
+to <bug-lilypond@gnu.org>.
+ Bugs that are not fault of LilyPond are documented here.
-CPPFLAGS are the preprocessor flags.
+Bison 1.875
+...........
-The configure script is Cygnus configure, and it will accept
---help. If you are not root, you will probably have to make
-it with a different --prefix option. Our favourite location
-is
+There is a bug in bison-1.875: compilation fails with "parse error
+before `goto'" in line 4922 due to a bug in bison. To fix, please
+recompile bison 1.875 with the following fix
+ $ cd lily; make out/parser.cc
+ $ vi +4919 out/parser.cc
+ # append a semicolon to the line containing "__attribute__ ((__unused__))
+ # save
+ $ make
+Solaris
+.......
+Solaris7, ./configure
+ `./configure' needs a POSIX compliant shell. On Solaris7, `/bin/sh'
+is not yet POSIX compliant, but `/bin/ksh' or bash is. Run configure
+like
+ CONFIG_SHELL=/bin/ksh ksh -c ./configure
- configure --prefix=$HOME/usr
+or
+ CONFIG_SHELL=/bin/bash bash -c ./configure
+FreeBSD
+.......
+To use system fonts, dejaview must be installed. With the default
+port, the fonts are installed in `usr/X11R6/lib/X11/fonts/dejavu'.
+ Open the file `$LILYPONDBASE/usr/etc/fonts/local.conf' and add the
+following line just after the `<fontconfig>' line. (Adjust as necessary
+for your hierarchy.)
-In this case, you will have to set up MFINPUTS, and TEXIN-
-PUTS accordingly.
+ <dir>/usr/X11R6/lib/X11/fonts</dir>
-Since GNU LilyPond currently is beta, you are advised to
-also use
+International fonts
+...................
+On MacOS X, all fonts are installed by default. However, finding all
+system fonts requires a bit of configuration; see this post
+(http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html)
+on the `lilypond-user' mailing list.
+ On Linux, international fonts are installed by different means on
+every distribution. We cannot list the exact commands or packages that
+are necessary, as each distribution is different, and the exact package
+names within each distribution changes. Here are some hints, though:
+Red Hat Fedora
+ taipeifonts fonts-xorg-truetype ttfonts-ja fonts-arabic \
+ ttfonts-zh_CN fonts-ja fonts-hebrew
+Debian GNU/Linux
- --enable-debugging
- --enable-checking
+ apt-get install emacs-intl-fonts xfonts-intl-.* \
+ ttf-kochi-gothic ttf-kochi-mincho \
+ xfonts-bolkhov-75dpi xfonts-cronyx-100dpi xfonts-cronyx-75dpi
-
-Options to configure include:
-
-
---enable-guile
- Link in GUILE (experimental)
-
---enable-printing
- Enable debugging print routines (lilypond -D option)
-
---enable-optimise
- Set maximum optimisation: compile with -O2. This can
- be unreliable on some compiler/platform combinations
- (eg, DEC Alpha and PPC)
-
---enable-profiling
- Compile with support for profiling.
-
---enable-config
- Output to a different configuration file. Needed for
- multi-platform builds
-
-All options are documented in the configure help The option
---enable-optimise is recommended for Real Life usage.
-
-If you do
-
-
-
-
-
-
- make all
-
-
-
-
-
-everything will be compiled, but nothing will be installed.
-The resulting binaries can be found in the subdirectories
-out/ (which contain all files generated during compilation).
-
-
-7: CONFIGURING FOR MULTIPLE PLATFORMS
-
-
-If you want to compile LilyPond with different configuration
-settings, then, you can use the --enable-config option.
-Example: suppose I want to build with and without profil-
-ing. Then I'd use the following for the normal build,
-
-
- configure --prefix=~ --disable-optimise --enable-checking
- make
- make install
-
-
-
-
-
-and for the profiling version, I specify a different config-
-uration.
-
-
-
-
-
-
- configure --prefix=~ --enable-profiling --enable-config=optprof --enable-optimise --disable-checking
- make config=optprof
- make config=optprof install
-
-
-
-
-
-
-8: INSTALLING
-
-
-If you have done a successful make, then a simple
-
-
-
-
-
-
- make install
-
-
-
-
-
-should do the trick.
-
-If you are doing an upgrade, please remember to remove obso-
-lete .pk and .tfm files of the fonts. A script has been
-provided to do the work for you, see bin/clean-fonts.sh.
-
-
-CAVEATS
-
-
-
-o The -O2 option to gcc triggers a gcc bug on DEC Alpha
- in dstream.cc. You should turn off this flag for this
-
-
- file.
-
-
-EXAMPLE
-
-
-This is what I type in my xterm:
-
-
-
-
-
-
- lilypond someinput.ly
- tex someinput.tex
- xdvi someinput&
-
-
-
-
-
-This is what the output looks like over here:
-
-
-
-
-
-
- GNU LilyPond 0.0.78 #4/FlowerLib 1.1.24 #0
- Parsing ... [/home/hw/share/lilypond/init//
- <..etc..>
- init//performer.ly]]][input/kortjakje.ly]
- Creating elements ...[8][16][24][25]
- Preprocessing elements...
- Calculating column positions ... [14][25]
- Postprocessing elements...
- TeX output to someinput.tex ...
- Creating MIDI elements ...MIDI output to someinput.midi ...
-
-
- hw:~/musix/spacer$ xdvi someinput&
- [1] 855
-
-
-
-
-
-Check out the input files, some of them have comments Please
-refer to the man page for more information.
-
-
-9: REDHAT LINUX
-
-
-RedHat Linux users can compile an RPM. A spec file is in
-make/out/lilypond.spec. You should install a gif file
-called lelie_icon.gif along with the sources. You can gen-
-erate this gif file by typing
-
-
-
-
-
-
- make gifs
-
-
-
-
-
-in the directory Documentation.
-
-You can make the rpm by issuing
-
-
-
-
-
-
- make rpm
-
-
-
-
-
-
-10: DEBIAN GNU/LINUX
-
-
-A Debian package is also available; contact Anthony Fok
-foka@debian.org <foka@debian.org>. The build scripts are in
-the subdirectory debian/
-
-
-11: WINDOWS NT/95
-
-
-Separate instructions on building for W32 are avaible in the
-file README-W32.yo.
-
-
-12: AUTHORS
-
-
-Han-Wen Nienhuys <hanwen@cs.uu.nl>
-
-Jan Nieuwenhuizen <janneke@gnu.org>
-
-Have fun!
projects / lilypond.git / blobdiff