3 @comment node-name, next, previous, up\input texinfo @c -*-texinfo-*-
4 @setfilename INSTALL.info
5 @settitle INSTALL - compiling and installing GNU LilyPond
7 @comment FIXME -- this information is getting rather stale
11 @chapter Compiling and installing on Unix
15 <a name="download-source">
20 Even numbered versions are `stable' (2.2, 2.4 etc), while odd version
21 are development releases (2.3, 2.5, etc). Building LilyPond is an
22 involved process, so if possible, download a precompiled binary from
23 @uref{http://lilypond.org/,the lilypond site}.
26 @subsection Source code
28 Download source tarballs from
30 @item Download development releases from
31 @uref{http://lilypond.org/download/} by HTTP.
32 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror).
36 Use Xdelta to patch tarballs, e.g. to patch
37 @file{lilypond-1.4.2.tar.gz} to @file{lilypond-1.4.3.tar.gz}, do
40 xdelta patch lilypond-1.4.2-1.4.3.xd lilypond-1.4.2.tar.gz
44 For information on packaging and CVS, see
45 @uref{http://lilypond.org/}, under ``development''.
48 @subsection Precompiled binaries
50 Check out @uref{http://lilypond.org} for up to date information on
54 @subsection Font problems
56 If you are upgrading from a previous version of LilyPond, be sure to
57 remove all old font files. These include @file{.pk} and @file{.tfm}
58 files that may be located in @file{/var/lib/texmf},
59 @file{/var/spool/texmf}, @file{/var/tmp/texmf} or
60 @file{@var{prefix}/share/lilypond/fonts/}. A script automating this
61 has been included, see @file{buildscripts/out/clean-fonts}.
66 @subsection Compilation
68 In addition to the packages needed for running Lilypond (see below),
69 you need the following extra packages for building.
71 When installing a binary package FOO, you may need to install the
72 FOO-devel or libFOO-dev package too.
76 @item @uref{http://fontforge.sf.net/,FontForge} 20041211 or newer.
78 @item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.1.0 or
81 You will need to install some additional packages to get mftrace to
84 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
85 (version 1.6.5 or newer). If you are installing binary packages, you
86 may need to install guile-devel or guile-dev or libguile-dev too.
88 @item @uref{http://www.gnu.org/software/flex/,Flex} (version 2.5.4a or newer).
90 WARNING: plain Flex 2.5.4(a) generates invalid C++ code. GCC 3.x
91 chokes on this. If you wish to use GCC 3.x, make sure that your
92 distribution supports g++ 3.x and flex. For workarounds, see
93 lexer-gcc-3.1.sh in the source directory.
97 @TeX{} is used as an optional output backend.
99 Also, @TeX{}'s libkpathsea is used to find the fonts (@file{.mf},
100 @file{.afm}, @file{.tfm}). Make sure you have tetex 1.0 or newer
101 (1.0.6 is known to work). If you are installing binary packages, you
102 may need to install tetex-devel, tetex-dev or libkpathsea-dev too.
105 @item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.7 or newer).
108 @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 3.1 or
109 newer). EGCS and 2.x are known to cause crashes.
111 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
113 @item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer).
115 @item @uref{http://www.gnu.org/software/bison/,Bison} (version 1.29 or
116 newer, but not 1.50 or 1.75).
118 @item @uref{http://www.gnu.org/software/gettext/gettext.html,gettext}.
120 @item All packages necessary for running, including headers.
124 @subsection Running requirements
126 Running LilyPond requires proper installation of the following
131 @item @uref{http://www.freetype.org/,Freetype} (version 2).
132 @item @uref{http://www.pango.org/,Pango} (version 1.6 or newer).
133 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
134 (version 1.6.5 or newer).
135 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
137 @item @uref{http://www.ghostscript.com,Ghostscript} (version 8.15 or
141 You have to help @TeX{} and MetaFont find LilyPond support files.
142 After compiling, scripts to do this can be found in
143 @file{buildscripts/out/lilypond-profile} and
144 @file{buildscripts/out/lilypond-login}.
146 @subsection Building documentation
148 You can view the documentation online at
149 @uref{http://lilypond.org/doc/}, but you can also build it locally.
150 This process requires a successful compile of lilypond. The
151 documentation is built by issuing
158 Building the website requires some additional tools and packages
161 @item @uref{http://lilypond.org/download/fonts,ec-fonts-mftraced}
162 @item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
166 The HTML files can be installed into the standard documentation path
171 make out=www web-install
176 @section Building LilyPond
178 To install GNU LilyPond, type
181 gunzip -c lilypond-x.y.z | tar xf -
183 ./configure # run with --help for applicable options
186 sh buildscripts/clean-fonts.sh
190 The most time-consuming part of compiling LilyPond is tracing the
191 Type1 fonts. You can shortcut this operation by issuing
192 one of the following commands
196 make -C mf get-pfa # requires rpm2cpio
197 make -C mf get-debian-pfa # may not be up to date
201 If you are doing an upgrade, you should remove all @file{feta}
202 @code{.pk} and @code{.tfm} files. A script has been provided to do the
203 work for you, see @file{buildscripts/out/clean-fonts}.
205 If you are not root, you should choose a @code{--prefix} argument that
206 points into your home directory, e.g.
209 ./configure --prefix=$HOME/usr
213 In this case, you have to insert the contents of
214 @code{buildscripts/out/lilypond-login} or
215 @code{buildscripts/out/lilypond-profile} into your start up scripts by
220 @subsection Configuring for multiple platforms
222 If you want to build multiple versions of LilyPond with different
223 configuration settings, you can use the @code{--enable-config=CONF}
224 option of configure. You should use @samp{make conf=CONF} to generate
225 the output in @file{out-CONF}. Example: Suppose you want to build
226 with and without profiling, then use the following for the normal
231 ./configure --prefix=$HOME/usr/ --enable-checking
237 and for the profiling version, specify a different configuration
241 ./configure --prefix=$HOME/usr/ --enable-profiling --enable-config=prof --disable-checking
243 make conf=prof install
250 An Emacs mode for entering music and running LilyPond is contained in
251 the source archive in the @file{elisp} directory. Do @command{make
252 install} to install it to @var{elispdir}. The file @file{lilypond-init.el}
253 should be placed to @var{load-path}@file{/site-start.d/} or appended
254 to your @file{~/.emacs} or @file{~/.emacs.el}.
256 As a user, you may want add your source path (e.g. @file{~/site-lisp/}) to
257 your @var{load-path} by appending the following line (as modified) to your
259 @c any reason we do not advise: (push "~/site-lisp" load-path)
262 (setq load-path (append (list (expand-file-name "~/site-lisp")) load-path))
269 A Vim mode for entering music and running LilyPond is contained in the
270 source archive in @code{$VIM} directory. For version 6.2 and newer,
271 Vim-mode works directly after installing LilyPond. Otherwise,
272 complete the following two steps.
274 For earlier versions (and if @code{$VIM} environment variable does not
275 fall-back to @file{/usr/local/share/vim}, see @code{:version} in vim),
276 the LilyPond file type is detected if your file @file{~/.vim/filetype.vim} @c
277 has the following content
280 if exists("did_load_filetypes")
283 augroup filetypedetect
284 au! BufNewFile,BufRead *.ly setf lilypond
288 If Vim has been (pre-)installed to @file{/usr/...} (or any other place)
289 instead of @file{/usr/local/...}, then @file{/usr/local/share/vim} may not
290 be specified in your @code{$VIMRUNTIME} environment variable and you have to
291 include this path explicitly by appending the following line to your
295 set runtimepath+=/usr/local/share/vim/
301 For help and questions use @email{lilypond-user@@gnu.org}. Send bug
302 reports to @email{bug-lilypond@@gnu.org}.
304 Bugs that are not fault of LilyPond are documented here.
306 @subsection Bison 1.875
308 There is a bug in bison-1.875: compilation fails with "parse error
309 before `goto'" in line 4922 due to a bug in bison. To fix, either
310 recompile bison 1.875 with the following fix
314 $ cd lily; make out/parser.cc
315 $ vi +4919 out/parser.cc
316 # append a semicolon to the line containing "__attribute__ ((__unused__))
322 @subsection Linking to kpathsea
324 If kpathsea and the corresponding header files are installed in some
325 directory where GCC does not search by default, for example in
326 @file{/usr/local/lib/} and @file{/usr/local/include/} respectively,
327 you have to explicitly tell configure where to find it. To do this
330 @item @code{rm config.cache}
331 @item @code{export LDFLAGS=-L/usr/share/texmf/lib}
332 @item @code{export CPPFLAGS=-I/usr/share/texmf/include}
333 @item @code{./configure}
335 Once configure has found them, the paths are stored in
336 @file{config.make} and will be used even if you don't have the
337 environment variables set during make.
340 @unnumberedsubsec Gcc-3.0.4
342 Gcc 3.0.4 is flaky; upgrade GCC.
344 @unnumberedsubsec Flex-2.5.4a and gcc-3.x
346 Flex 2.5.4a does not produce g++-3.1.1 compliant C++ code. To compile
347 LilyPond with gcc-3.1.1 or higher you may do
351 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
352 CPPFLAGS=-I$(pwd)/lily/out-gcc-3.1 CC=gcc-3.1 CXX=g++-3.1 \
353 ./configure --enable-config=gcc-3.1
354 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
360 @unnumberedsubsec OpenBSD
364 Refer to the section ``Linking to kpathsea'': GCC on OpenBSD doesn't
365 set include paths for kpathsea.
368 @unnumberedsubsec NetBSD
371 @item The flex precompiled in NetBSD-1.4.2 is broken.
372 Upgrade to flex-2.5.4a.
375 @unnumberedsubsec Solaris
378 @item Solaris7, ./configure
380 @file{./configure} needs a POSIX compliant shell. On Solaris7,
381 @file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash
382 is. Run configure like
385 CONFIG_SHELL=/bin/ksh ksh -c ./configure
391 CONFIG_SHELL=/bin/bash bash -c ./configure