1 \input texinfo @c -*-texinfo-*-
2 @setfilename INSTALL.info
3 @settitle INSTALL - compiling and installing GNU LilyPond
10 @chapter Compiling and installing on Unix
14 <a name="download-source">
19 Even numbered minor versions are `stable' (2.2, 2.4 etc), while odd
20 version are development releases (2.3, 2.5, etc). Building LilyPond
21 is an involved process. If possible, from
22 @uref{http://lilypond.org/download,download a precompiled binary}
25 @subsection Source code
31 @uref{http://lilypond.org/download/} by HTTP.
32 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror).
35 CVS from @uref{http://savannah.gnu.org/cvs/?group=lilypond,savannah.gnu.org}
39 CVS_RSH=ssh cvs -d:ext:anoncvs@@savannah.gnu.org:/cvsroot/lilypond co lilypond
42 The CVS repository does not contain generated files. To create
50 For information on packaging, see @uref{http://lilypond.org/devel}.
52 @subsection Precompiled binary packages
54 Check out @uref{http://lilypond.org/download} for up to date information on
55 binary packages for your platform.
58 @subsection Font problems
60 If you are upgrading from a previous version of LilyPond, be sure to
61 remove all old font files. These include @file{.pk} and @file{.tfm}
62 files that may be located in @file{/var/lib/texmf},
63 @file{/var/spool/texmf}, @file{/var/tmp/texmf} or
64 @file{@var{prefix}/share/lilypond/fonts/}. A script automating this
65 has been included, see @file{buildscripts/out/clean-fonts}.
70 @subsection Compilation
72 In addition to the packages needed for running Lilypond (see below),
73 you need the following extra packages for building.
75 When installing a binary package FOO, you may need to install the
76 FOO-devel, libFOO-dev or FOO-dev package too.
80 @item @uref{http://fontforge.sf.net/,FontForge} 20041211 or newer.
82 @item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.1.0 or
85 You will need to install some additional packages to get mftrace to
88 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
89 (version 1.6.5 or newer). If you are installing binary packages, you
90 may need to install guile-devel or guile-dev or libguile-dev too.
92 @item @uref{http://www.gnu.org/software/flex/,Flex} (version 2.5.4a or newer).
94 WARNING: plain Flex 2.5.4(a) generates invalid C++ code. GCC 3.x
95 chokes on this. If you wish to use GCC 3.x, make sure that your
96 distribution supports g++ 3.x and flex. For workarounds, see
97 lexer-gcc-3.1.sh in the source directory.
101 @TeX{} is used as an optional output backend.
103 Also, @TeX{}'s libkpathsea is used to find the fonts (@file{.mf},
104 @file{.afm}, @file{.tfm}). Make sure you have tetex 1.0 or newer
105 (1.0.6 is known to work). If you are installing binary packages, you
106 may need to install tetex-devel, tetex-dev or libkpathsea-dev too.
109 @item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.7 or newer).
112 @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 3.1 or
113 newer). EGCS and 2.x are known to cause crashes.
115 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
117 @item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer).
119 @item @uref{http://www.gnu.org/software/bison/,Bison} (version 1.29 or
120 newer, but not 1.50 or 1.75).
122 @item @uref{http://www.gnu.org/software/gettext/gettext.html,gettext}.
124 @item All packages required for running, including development packages with
125 header files and libraries.
129 @subsection Running requirements
131 Running LilyPond requires proper installation of the following
136 @item @uref{http://www.freetype.org/,Freetype} (version 2).
137 @item @uref{http://www.pango.org/,Pango} (version 1.6 or newer).
138 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
139 (version 1.6.5 or newer).
140 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
142 @item @uref{http://www.ghostscript.com,Ghostscript} (version 8.15 or
146 You have to help @TeX{} and MetaFont find LilyPond support files.
147 After compiling, scripts to do this can be found in
148 @file{buildscripts/out/lilypond-profile} and
149 @file{buildscripts/out/lilypond-login}.
151 @subsection Building documentation
153 You can view the documentation online at
154 @uref{http://lilypond.org/doc/}, but you can also build it locally.
155 This process requires a successful compile of lilypond. The
156 documentation is built by issuing
163 Building the website requires some additional tools and packages
166 @item @uref{http://lilypond.org/download/fonts,ec-fonts-mftraced}
167 @item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
171 The HTML files can be installed into the standard documentation path
176 make out=www web-install
181 @section Building LilyPond
183 To install GNU LilyPond, type
186 gunzip -c lilypond-x.y.z | tar xf -
188 ./configure # run with --help for applicable options
191 sh buildscripts/clean-fonts.sh
195 The most time-consuming part of compiling LilyPond is tracing the
196 Type1 fonts. You can shortcut this operation by issuing
197 one of the following commands
201 make -C mf get-pfa # requires rpm2cpio
202 make -C mf get-debian-pfa # may not be up to date
206 If you are doing an upgrade, you should remove all @file{feta}
207 @code{.pk} and @code{.tfm} files. A script has been provided to do the
208 work for you, see @file{buildscripts/out/clean-fonts}.
210 If you are not root, you should choose a @code{--prefix} argument that
211 points into your home directory, e.g.
214 ./configure --prefix=$HOME/usr
218 In this case, you have to insert the contents of
219 @code{buildscripts/out/lilypond-login} or
220 @code{buildscripts/out/lilypond-profile} into your start up scripts by
225 @subsection Configuring for multiple platforms
227 If you want to build multiple versions of LilyPond with different
228 configuration settings, you can use the @code{--enable-config=CONF}
229 option of configure. You should use @samp{make conf=CONF} to generate
230 the output in @file{out-CONF}. Example: Suppose you want to build
231 with and without profiling, then use the following for the normal
236 ./configure --prefix=$HOME/usr/ --enable-checking
242 and for the profiling version, specify a different configuration
246 ./configure --prefix=$HOME/usr/ --enable-profiling --enable-config=prof --disable-checking
248 make conf=prof install
255 An Emacs mode for entering music and running LilyPond is contained in
256 the source archive in the @file{elisp} directory. Do @command{make
257 install} to install it to @var{elispdir}. The file @file{lilypond-init.el}
258 should be placed to @var{load-path}@file{/site-start.d/} or appended
259 to your @file{~/.emacs} or @file{~/.emacs.el}.
261 As a user, you may want add your source path (e.g. @file{~/site-lisp/}) to
262 your @var{load-path} by appending the following line (as modified) to your
264 @c any reason we do not advise: (push "~/site-lisp" load-path)
267 (setq load-path (append (list (expand-file-name "~/site-lisp")) load-path))
274 A Vim mode for entering music and running LilyPond is contained in the
275 source archive in @code{$VIM} directory. For version 6.2 and newer,
276 Vim-mode works directly after installing LilyPond. Otherwise,
277 complete the following two steps.
279 For earlier versions (and if @code{$VIM} environment variable does not
280 fall-back to @file{/usr/local/share/vim}, see @code{:version} in vim),
281 the LilyPond file type is detected if your file @file{~/.vim/filetype.vim} @c
282 has the following content
285 if exists("did_load_filetypes")
288 augroup filetypedetect
289 au! BufNewFile,BufRead *.ly setf lilypond
293 If Vim has been (pre-)installed to @file{/usr/...} (or any other place)
294 instead of @file{/usr/local/...}, then @file{/usr/local/share/vim} may not
295 be specified in your @code{$VIMRUNTIME} environment variable and you have to
296 include this path explicitly by appending the following line to your
300 set runtimepath+=/usr/local/share/vim/
306 For help and questions use @email{lilypond-user@@gnu.org}. Send bug
307 reports to @email{bug-lilypond@@gnu.org}.
309 Bugs that are not fault of LilyPond are documented here.
311 @subsection Bison 1.875
313 There is a bug in bison-1.875: compilation fails with "parse error
314 before `goto'" in line 4922 due to a bug in bison. To fix, either
315 recompile bison 1.875 with the following fix
319 $ cd lily; make out/parser.cc
320 $ vi +4919 out/parser.cc
321 # append a semicolon to the line containing "__attribute__ ((__unused__))
327 @subsection Linking to kpathsea
329 If kpathsea and the corresponding header files are installed in some
330 directory where GCC does not search by default, for example in
331 @file{/usr/local/lib/} and @file{/usr/local/include/} respectively,
332 you have to explicitly tell configure where to find it. To do this
335 @item @code{rm config.cache}
336 @item @code{export LDFLAGS=-L/usr/share/texmf/lib}
337 @item @code{export CPPFLAGS=-I/usr/share/texmf/include}
338 @item @code{./configure}
340 Once configure has found them, the paths are stored in
341 @file{config.make} and will be used even if you don't have the
342 environment variables set during make.
345 @unnumberedsubsec Gcc-3.0.4
347 Gcc 3.0.4 is flaky; upgrade GCC.
349 @unnumberedsubsec Flex-2.5.4a and gcc-3.x
351 Flex 2.5.4a does not produce g++-3.1.1 compliant C++ code. To compile
352 LilyPond with gcc-3.1.1 or higher you may do
356 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
357 CPPFLAGS=-I$(pwd)/lily/out-gcc-3.1 CC=gcc-3.1 CXX=g++-3.1 \
358 ./configure --enable-config=gcc-3.1
359 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
365 @unnumberedsubsec OpenBSD
369 Refer to the section ``Linking to kpathsea'': GCC on OpenBSD doesn't
370 set include paths for kpathsea.
373 @unnumberedsubsec NetBSD
376 @item The flex precompiled in NetBSD-1.4.2 is broken.
377 Upgrade to flex-2.5.4a.
380 @unnumberedsubsec Solaris
383 @item Solaris7, ./configure
385 @file{./configure} needs a POSIX compliant shell. On Solaris7,
386 @file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash
387 is. Run configure like
390 CONFIG_SHELL=/bin/ksh ksh -c ./configure
396 CONFIG_SHELL=/bin/bash bash -c ./configure