1 @c -*- coding: us-ascii; mode: texinfo; -*-
3 @node Compiling LilyPond
4 @chapter Compiling LilyPond
7 * Compiling from source::
8 * Concurrent Stable and Development Versions::
11 @node Compiling from source
12 @section Compiling from source
14 TODO (see AU 1 for now)
15 @c currently broken; will fix after 2.14
16 @c @include compile.itely
19 @node Concurrent Stable and Development Versions
20 @section Concurrent Stable and Development Versions
22 It can be useful to have both the stable and the development versions
23 of Lilypond available at once. One way to do this on GNU/Linux is to
24 install the stable version using the precompiled binary, and run the
25 development version from the source tree. After running @command{make
26 all} from the top directory of the Lilypond source files, there will
27 be a binary called @code{lilypond} in the @code{out} directory:
30 <@var{path to}>/lilypond/out/bin/lilypond
33 This binary can be run without actually doing the @code{make
34 install} command. The advantage to this is that you can have all
35 of the latest changes available after pulling from git and running
36 @code{make all}, without having to uninstall the old version and
39 So, to use the stable version, install it as usual and use the
46 To use the development version, create a link to the binary in the
47 source tree by saving the following line in a file somewhere in your
51 exec <@var{path to}>/lilypond/out/bin/lilypond "$@@"
54 Save it as @code{Lilypond} (with a capital L to distinguish it
55 from the stable @code{lilypond}), and make it executable:
61 Then you can invoke the development version this way:
70 - how to build with debug info
72 - other compilation tricks for developers