3 @comment node-name, next, previous, up\input texinfo @c -*-texinfo-*-
4 @setfilename INSTALL.info
5 @settitle INSTALL - compiling and installing GNU LilyPond
9 @chapter Compiling and installing on Unix
13 <a name="download-source">
18 Even numbered versions are `stable' (2.0, 1.8 etc), while odd version
19 are development releases (1.9, 1.7 etc). Building LilyPond is an
20 involved process, so if possible, download a precompiled binary from
21 @uref{http://www.lilypond.org/,the lilypond site}.
24 @subsection Source code
26 Download source tarballs from here:
28 @item Download development releases from
29 @uref{ftp://ftp.lilypond.org/pub/LilyPond/} by FTP and
30 @uref{http://www.lilypond.org/ftp/} by HTTP.
31 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror).
35 Use Xdelta to patch tarballs, e.g. to patch
36 @file{lilypond-1.4.2.tar.gz} to @file{lilypond-1.4.3.tar.gz}, do
38 xdelta patch lilypond-1.4.2-1.4.3.xd lilypond-1.4.2.tar.gz
41 For information on packaging and CVS, see
42 @uref{http://lilypond.org/}, under ``development''.
45 @subsection Precompiled binaries
47 Check out @uref{http://lilypond.org} for up to date information on
51 @subsection Font problems
53 If you are upgrading from a previous version of LilyPond, be sure to
54 remove all old font files. These include @file{.pk} and @file{.tfm} files
55 that may be located in @file{/var/lib/texmf}, @file{/var/spool/texmf},
56 @file{/var/tmp/texmf} or @file{@var{prefix}/share/lilypond/fonts/}. A
57 script automating this has been included, see
58 @file{buildscripts/clean-fonts.sh}.
65 @subsection Compilation
67 You need the following packages to compile LilyPond:
71 @uref{http://gcc.gnu.org/,
72 The GNU c++ compiler} (version 3.1 or newer).
73 EGCS and 2.x are known to cause crashes.
75 @item @uref{http://www.python.org,Python} (version 2.1 or newer).
77 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} (version 1.6.0 or newer).
79 @item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer).
81 @item @uref{http://www.gnu.org/software/flex/,Flex} (version 2.5.4a or newer).
83 WARNING: plain Flex 2.5.4(a) generates invalid C++ code. GCC 3.x
84 chokes on this. If you wish to use GCC 3.x, make sure that your
85 distribution supports g++ 3.x and flex. For workarounds, see
86 lexer-gcc-3.1.sh in the source directory.
88 @item @uref{http://www.gnu.org/software/bison/,Bison} (version 1.25 or
89 newer, but not 1.50 or 1.75).
93 @TeX{} is used as an output backend.
95 Also, @TeX{}'s libkpathsea is used to find the fonts (@file{.mf},
96 @file{.afm}, @file{.tfm}). Make sure you have tetex 1.0 or newer
97 (1.0.6 is known to work). You may need to install a tetex-devel (or
98 tetex-dev or libkpathsea-dev) package too.
100 @item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.6 or newer).
103 @uref{ftp://ftp.ctan.org/tex-archive/macros/latex/contrib/supported/geometry,geometry
106 This package is normally included with the @TeX{} distribution.
108 @item kpathsea, a library for searching (@TeX{}) files.
110 @item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.0.17 or
113 You will need to install some additional packages to get mftrace to
118 @subsection Running requirements
120 GNU LilyPond does use a lot of resources. For operation you need the
125 @item Xdvi and Ghostscript.
126 @item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} 1.6.0, or newer.
129 You have to help @TeX{} and MetaFont find LilyPond support
130 files. After compiling, scripts to do this can be found in
131 @file{buildscripts/out/lilypond-profile} and
132 @file{buildscripts/out/lilypond-login}.
134 @subsection Building documentation
136 You can view the documentation online at
137 @uref{http://www.lilypond.org/doc/}, but you can also build it
138 locally. This process requires a successful compile of lilypond. The
139 documentation is built by issuing:
144 Building the website requires some additional tools:
147 @item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
151 The HTML files can be installed into the standard documentation path
155 make out=www web-install
159 @section Building LilyPond
161 To install GNU LilyPond, type
163 gunzip -c lilypond-x.y.z | tar xf -
165 ./configure # run with --help to see appropriate options
168 sh buildscripts/clean-fonts.sh
171 The most time-consuming part of compiling LilyPond is tracing the
172 Type1 fonts. You can shortcut this operation by issuing
173 one of the following commands:
176 make -C mf get-pfa # requires rpm2cpio
177 make -C mf get-debian-pfa # may not be up to date
180 If you are doing an upgrade, you should remove all @file{feta}
181 @code{.pk} and @code{.tfm} files. A script has been provided to do the
182 work for you, see @file{buildscripts/clean-fonts.sh}.
184 If you are not root, you should choose a @code{--prefix} argument that
185 points into your home directory, e.g.:
187 ./configure --prefix=$HOME/usr
190 In this case, you have to insert the contents of
191 @code{buildscripts/out/lilypond-login} or
192 @code{buildscripts/out/lilypond-profile} into your start up scripts by
197 @subsection Configuring for multiple platforms
199 If you want to build multiple versions of LilyPond with different
200 configuration settings, you can use the @code{--enable-config=CONF}
201 option of configure. You should use @samp{make conf=CONF} to generate
202 the output in @file{out-CONF}. Example: Suppose I want to build with
203 and without profiling. Then I'd use the following for the normal
207 ./configure --prefix=$HOME/usr/ --enable-checking
212 and for the profiling version, I specify a different configuration:
215 ./configure --prefix=$HOME/usr/ --enable-profiling --enable-config=prof --disable-checking
217 make conf=prof install
224 An Emacs mode for entering music and running LilyPond is contained in
225 the source archive in the @file{elisp} directory. @command{make
226 install} installs it @var{elispdir}. The file @file{lilypond-init.el}
227 should be placed to @var{load-path}@file{/site-start.d/} or appended
228 to your @file{~/.emacs} or @file{~/.emacs.el}.
230 As a user, you may want add your source path or, e.g., @file{~/site-lisp/}
231 to your @var{load-path}. Append the following line (modified) to your
233 @c any reason we do not advise: (push "~/site-lisp" load-path)
236 (setq load-path (append (list (expand-file-name "~/site-lisp")) load-path))
243 @c lilypond.words.el for vim auto-completion?
244 A Vim mode for entering music and running LilyPond is contained in
245 the source archive. Append the content of @file{vimrc} to @file{~/.vimrc}
246 to get shortcuts. Install file @file{lilypond.words.el} to @file{~/.vim/} to
247 get auto-completion. Syntax highlighting you get by installing files
248 @file{lilypond.vim} and @file{lilypond.words.vim} to @file{~/.vim/syntax/}
249 and appending the following to @file{~/.vim/filetype.vim}:
253 if exists("did_load_filetypes")
256 augroup filetypedetect
257 au! BufRead,BufNewFile *.ly setfiletype lilypond
266 For help and questions use @email{lilypond-user@@gnu.org}. Send bug
267 reports to @email{bug-lilypond@@gnu.org}.
269 Bugs that are not fault of LilyPond are documented here.
271 @subsection Linking to kpathsea
273 If kpathsea and the corresponding header files are installed in some
274 directory where GCC does not search by default, for example in
275 @file{/usr/local/lib/} and @file{/usr/local/include/} respectively,
276 you have to explicitly tell configure where to find it. To do this:
279 @item @code{rm config.cache}
280 @item @code{export LDFLAGS=-L/usr/share/texmf/lib}
281 @item @code{export CPPFLAGS=-I/usr/share/texmf/include}
282 @item @code{./configure}
284 Once configure has found them, the paths are stored in
285 @file{config.make} and will be used even if you don't have the
286 environment variables set during make.
289 @unnumberedsubsec Gcc-3.0.4
291 Gcc 3.0.4 is flaky; upgrade GCC.
293 @unnumberedsubsec Flex-2.5.4a and gcc-3.x
295 Flex 2.5.4a does not produce g++-3.1.1 compliant C++ code. To compile
296 LilyPond with gcc-3.1.1 you may do
299 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
300 CPPFLAGS=-I$(pwd)/lily/out-gcc-3.1 CC=gcc-3.1 CXX=g++-3.1 \
301 ./configure --enable-config=gcc-3.1
302 CONF=gcc-3.1 ./lexer-gcc-3.1.sh
307 @unnumberedsubsec OpenBSD
311 Refer to the section ``Linking to kpathsea'': GCC on OpenBSD doesn't
312 set include paths for kpathsea.
315 @unnumberedsubsec NetBSD
318 @item The flex precompiled in NetBSD-1.4.2 is broken.
319 Upgrade to flex-2.5.4a.
322 @unnumberedsubsec Solaris
325 @item Solaris7, ./configure
327 @file{./configure} needs a POSIX compliant shell. On Solaris7,
328 @file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash
329 is. Run configure like:
331 CONFIG_SHELL=/bin/ksh ksh -c ./configure
335 CONFIG_SHELL=/bin/bash bash -c ./configure