1 \input texinfo @c -*-texinfo-*-
2 @setfilename INSTALL.info
3 @settitle INSTALL - compiling and installing GNU LilyPond
5 @documentencoding utf-8
13 @chapter Compiling and installing on Unix
17 <a name="download-source">
22 Even numbered minor versions are `stable' (2.4, 2.6 etc), while odd
23 version are development releases (2.5, 2.7, etc). Building LilyPond
24 is an involved process. If possible
25 @uref{http://lilypond.org/download,download a precompiled binary}
28 @subsection Source code
34 @uref{http://lilypond.org/download/} by HTTP.
35 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror).
38 CVS from @uref{http://savannah.gnu.org/cvs/?group=lilypond,savannah.gnu.org}
42 CVS_RSH=ssh cvs -d:ext:anoncvs@@savannah.gnu.org:/cvsroot/lilypond co lilypond
45 The CVS repository does not contain generated files. To create
53 For information on packaging, see @uref{http://lilypond.org/devel}.
55 @subsection Precompiled binary packages
57 Check out @uref{http://lilypond.org/web/install/} for up to date
58 information on binary packages for your platform.
63 @subsection Compilation
65 In addition to the packages needed for running Lilypond (see below),
66 you need the following extra packages for building.
68 When installing a binary package FOO, you may need to install the
69 FOO-devel, libFOO-dev or FOO-dev package too.
73 @item @uref{http://fontforge.sf.net/,FontForge} 20050624 or newer.
75 @item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.1.9 or
78 You will need to install some additional packages to get mftrace to
81 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
82 (version 1.6.5 or newer). If you are installing binary packages, you
83 may need to install guile-devel or guile-dev or libguile-dev too.
85 @item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.8 or newer).
88 @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 3.3 or
89 newer). EGCS and 2.x are known to cause crashes.
91 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
93 @item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer).
95 @item @uref{http://www.gnu.org/software/gettext/gettext.html,gettext}.
98 @item @uref{http://www.gnu.org/software/flex/,Flex}
100 @item @uref{http://www.perl.org/,Perl}
102 @item @uref{http://www.gnu.org/software/flex/,GNU Bison}
104 @item All packages required for running, including development packages with
105 header files and libraries.
109 @subsection Running requirements
111 Running LilyPond requires proper installation of the following
116 @item @uref{http://www.freetype.org/,Freetype} (version 2).
117 @item @uref{http://www.freetype.org/,FontConfig} (version 2.2).
118 @item @uref{http://www.pango.org/,Pango} (version 1.6 or newer).
119 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
120 (version 1.6.5 or newer).
121 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
122 @item @uref{http://www.ghostscript.com,Ghostscript} (version 8.15 or
126 @subsection Building documentation
128 You can view the documentation online at
129 @uref{http://lilypond.org/doc/}, but you can also build it locally.
130 This process requires a successful compile of lilypond. The
131 documentation is built by issuing
138 Building the website requires some additional tools and packages
141 @item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
143 @item International fonts (see input/regression/utf-8.ly for hints
144 about which font packages are necessary for your platform)
145 @item Ghostscript, 8.15 with the patch from
146 @uref{http://bugs.ghostscript.com/show_bug.cgi?id=688154}
150 The HTML files can be installed into the standard documentation path
155 make out=www web-install
160 @section Building LilyPond
162 To install GNU LilyPond, type
165 gunzip -c lilypond-x.y.z | tar xf -
167 ./configure # run with --help for applicable options
173 The most time-consuming part of compiling LilyPond is tracing the
174 Type1 fonts. You can shortcut this operation by issuing
175 one of the following commands
179 make -C mf get-pfa # requires rpm2cpio
180 make -C mf get-debian-pfa # may not be up to date
184 If you are not root, you should choose a @code{--prefix} argument that
185 points into your home directory, e.g.
188 ./configure --prefix=$HOME/usr
193 @subsection Configuring for multiple platforms
195 If you want to build multiple versions of LilyPond with different
196 configuration settings, you can use the @code{--enable-config=CONF}
197 option of configure. You should use @samp{make conf=CONF} to generate
198 the output in @file{out-CONF}. Example: Suppose you want to build
199 with and without profiling, then use the following for the normal
204 ./configure --prefix=$HOME/usr/ --enable-checking
210 and for the profiling version, specify a different configuration
214 ./configure --prefix=$HOME/usr/ --enable-profiling --enable-config=prof --disable-checking
216 make conf=prof install
223 An Emacs mode for entering music and running LilyPond is contained in
224 the source archive in the @file{elisp} directory. Do @command{make
225 install} to install it to @var{elispdir}. The file @file{lilypond-init.el}
226 should be placed to @var{load-path}@file{/site-start.d/} or appended
227 to your @file{~/.emacs} or @file{~/.emacs.el}.
229 As a user, you may want add your source path (e.g. @file{~/site-lisp/}) to
230 your @var{load-path} by appending the following line (as modified) to your
232 @c any reason we do not advise: (push "~/site-lisp" load-path)
235 (setq load-path (append (list (expand-file-name "~/site-lisp")) load-path))
242 A Vim mode for entering music and running LilyPond is contained in the
243 source archive in @code{$VIM} directory.
245 The LilyPond file type is detected if the file @file{~/.vim/filetype.vim} @c
246 has the following content
249 if exists("did_load_filetypes")
252 augroup filetypedetect
253 au! BufNewFile,BufRead *.ly setf lilypond
258 Please include this path by appending the following line to your
263 set runtimepath+=/usr/local/share/lilypond/$@{LILYPOND_VERSION@}/vim/
268 where $@{LILYPOND_VERISON@} is your lilypond version. If Lilypond was not
269 installed in @file{/usr/local/}, then change this path accordingly.
274 For help and questions use @email{lilypond-user@@gnu.org}. Send bug
275 reports to @email{bug-lilypond@@gnu.org}.
277 Bugs that are not fault of LilyPond are documented here.
279 @subsection Bison 1.875
281 There is a bug in bison-1.875: compilation fails with "parse error
282 before `goto'" in line 4922 due to a bug in bison. To fix, please
283 recompile bison 1.875 with the following fix
287 $ cd lily; make out/parser.cc
288 $ vi +4919 out/parser.cc
289 # append a semicolon to the line containing "__attribute__ ((__unused__))
295 @subsection Linking to kpathsea
297 If kpathsea and the corresponding header files are installed in some
298 directory where GCC does not search by default, for example in
299 @file{/usr/local/lib/} and @file{/usr/local/include/} respectively,
300 you have to explicitly tell configure where to find it. To do this
303 @item @code{rm config.cache}
304 @item @code{export LDFLAGS=-L/usr/share/texmf/lib}
305 @item @code{export CPPFLAGS=-I/usr/share/texmf/include}
306 @item @code{./configure}
308 Once configure has found them, the paths are stored in
309 @file{config.make} and will be used even if you don't have the
310 environment variables set during make.
313 @unnumberedsubsec Gcc-3.0.4
315 Gcc 3.0.4 is flaky; upgrade GCC.
317 @unnumberedsubsec Flex-2.5.4a and gcc-3.x
319 Flex 2.5.4a does not produce g++-3.1.1 compliant C++ code. To compile
320 LilyPond with gcc-3.1.1 or higher you may do
324 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
325 CPPFLAGS=-I$(pwd)/lily/out-gcc-3.1 CC=gcc-3.1 CXX=g++-3.1 \
326 ./configure --enable-config=gcc-3.1
327 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
332 @unnumberedsubsec MacOS X
334 For Fink, use the following command to compile.
337 export GUILE=guile-1.6
338 export GUILE_CONFIG=guile-1.6-config
339 export PKG_CONFIG_PATH=/sw/lib/freetype219/lib/pkgconfig/:/sw/lib/fontconfig2/lib/pkgconfig/
340 ./configure --without-kpathsea
343 @unnumberedsubsec OpenBSD
347 Refer to the section ``Linking to kpathsea'': GCC on OpenBSD doesn't
348 set include paths for kpathsea.
351 @unnumberedsubsec NetBSD
354 @item The flex precompiled in NetBSD-1.4.2 is broken.
355 Upgrade to flex-2.5.4a.
358 @unnumberedsubsec Solaris
361 @item Solaris7, ./configure
363 @file{./configure} needs a POSIX compliant shell. On Solaris7,
364 @file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash
365 is. Run configure like
368 CONFIG_SHELL=/bin/ksh ksh -c ./configure
374 CONFIG_SHELL=/bin/bash bash -c ./configure