1 @c -*- coding: utf-8; mode: texinfo; -*-
4 @c DO NOT TRANSLATE THIS FILE
6 @c include any node/sections from the higher-level *texi file.
7 @c @n ode Compiling from source
8 @c @s ection Compiling from source
11 * Overview of compiling::
13 * Getting the source code::
15 * Compiling LilyPond::
16 * Post-compilation options::
18 * Concurrent stable and development versions::
23 @node Overview of compiling
24 @section Overview of compiling
26 Compiling LilyPond from source is an involved process, and is only
27 recommended for developers and packagers. Typical program users
28 are instead encouraged to obtain the program from a package
29 manager (on Unix) or by downloading a precompiled binary
30 configured for a specific operating system. Pre-compiled binaries
31 are available on the @rweb{Download} page.
33 Compiling LilyPond from source is necessary if you want to build,
34 install, or test your own version of the program.
36 A successful compile can also be used to generate and install the
37 documentation, incorporating any changes you may have made.
38 However, a successful compile is not a requirement for generating
39 the documentation. The documentation can be built using a Git
40 repository in conjunction with a locally installed copy of the
41 program. For more information, see @ref{Building documentation
44 Attempts to compile LilyPond natively on Windows have been
45 unsuccessful, though a workaround is available (see
54 * Requirements for running LilyPond::
55 * Requirements for compiling LilyPond::
56 * Requirements for building documentation::
60 @node Requirements for running LilyPond
61 @subsection Requirements for running LilyPond
63 Running LilyPond requires proper installation of the following
67 @item @uref{http://www.dejavu-fonts.org/, DejaVu fonts} (normally
70 @item @uref{http://www.fontconfig.org/, FontConfig} (2.4.0 or newer)
72 @item @uref{http://www.freetype.org/, Freetype} (2.1.10 or newer)
74 @item @uref{http://www.ghostscript.com, Ghostscript} (8.60 or
77 @item @uref{http://www.gnu.org/software/guile/guile.html, Guile}
80 @item @uref{http://www.pango.org/, Pango} (1.12 or newer)
82 @item @uref{http://www.python.org, Python} (2.4 or newer)
85 International fonts are required to create music with
86 international text or lyrics.
89 @node Requirements for compiling LilyPond
90 @subsection Requirements for compiling LilyPond
92 Below is a full list of packages needed to build LilyPond.
93 However, for most common distributions there is an easy way of
94 installing most all build dependencies in one go:
96 @multitable @columnfractions .5 .5
97 @headitem Distribution @tab Command
99 @tab @code{sudo apt-get build-dep lilypond}
102 @tab @code{sudo yum-builddep lilypond}
105 @c sorry for the idiosyncratic command, I really asked and argued
106 @c for "zypper build-dep" :-(
107 @tab @code{sudo zypper --build-deps-only source-install lilypond}
111 @item Everything listed in @ref{Requirements for running
114 @item Development packages for the above items (which should
115 include header files and libraries).
119 @c ghostscript-devel-[version] isn't needed
121 guile-devel-@var{version}
122 fontconfig-devel-@var{version}
123 freetype-devel-@var{version}
124 pango-devel-@var{version}
125 python-devel-@var{version}
130 @c libgs-dev isn't needed
132 guile-@var{version}-dev
136 python@var{version}-dev
139 @item @uref{http://flex.sourceforge.net/, Flex}
141 @item @uref{http://fontforge.sf.net/, FontForge} (20060125 or
142 newer; 20100501 or newer is recommended; must be compiled
143 with @option{--enable-double}. Failure to do so can lead to
144 poor intersection calculations and poorly-rendered glyphs.)
146 @item @uref{http://www.gnu.org/software/bison/, GNU Bison}
148 @item @uref{http://gcc.gnu.org/, GNU Compiler Collection} (3.4 or
149 newer, 4.@var{x} recommended)
151 @item @uref{http://www.gnu.org/software/gettext/gettext.html, GNU
152 gettext} (0.17 or newer)
154 @item @uref{http://www.gnu.org/software/make/, GNU Make} (3.78 or
157 @item @uref{http://metafont.tutorial.free.fr/, MetaFont}
158 (mf-nowin, mf, mfw or mfont binaries), usually packaged with
159 @uref{http://www.latex-project.org/ftp.html, @TeX{}}.
161 @item @uref{http://cm.bell-labs.com/who/hobby/MetaPost.html,
162 MetaPost} (mpost binary), usually packaged with
163 @uref{http://www.latex-project.org/ftp.html, @TeX{}}.
165 @item @uref{http://www.perl.org/, Perl}
167 @item @uref{http://www.gnu.org/software/texinfo/, Texinfo} (4.11
170 @item @uref{http://www.lcdf.org/~eddietwo/type/#t1utils, Type 1
171 utilities} (1.33 or newer recommended)
175 @node Requirements for building documentation
176 @subsection Requirements for building documentation
178 You can view the documentation online at
179 @uref{http://www.lilypond.org/doc/}, but you can also build it
180 locally. This process requires some additional tools and
184 @item Everything listed in @ref{Requirements for compiling
187 @item @uref{http://www.imagemagick.org/, ImageMagick}
189 @item @uref{http://netpbm.sourceforge.net/, Netpbm}
191 @item @uref{http://gzip.org/, gzip}
193 @item @uref{http://rsync.samba.org/, rsync}
195 @item @uref{http://www.nongnu.org/texi2html/, Texi2HTML} (1.82)
197 @item International fonts
225 @node Getting the source code
226 @section Getting the source code
229 @subheading Downloading the Git repository
231 In general, developers compile LilyPond from within a local Git
232 repository. Setting up a local Git repository is explained in
233 @rcontrib{Starting with Git}.
236 @subheading Downloading a source tarball
238 Packagers are encouraged to use source tarballs for compiling.
240 The tarball for the latest stable release is available on the
245 @uref{http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=snapshot, source code snapshot}
246 is also available as a tarball from the GNU Savannah Git server.
249 All tagged releases (including legacy stable
250 versions and the most recent development release) are available
254 @uref{http://download.linuxaudio.org/lilypond/source/}
257 Download the tarball to your @file{~/src/} directory, or some
258 other appropriate place.
260 @warning{Be careful where you unpack the tarball! Any
261 subdirectories of the current folder named @file{lilypond/} or
262 @file{lilypond-@var{x.y.z}/} (where @var{x.y.z} is the release
263 number) will be overwritten if there is a name clash with the
266 Unpack the tarball with this command:
269 tar -xzf lilypond-@var{x.y.z}.tar.gz
272 This creates a subdirectory within the current directory called
273 @file{lilypond-@var{x.y.z}/}. Once unpacked, the source files
274 occupy about 40 MB of disk space.
276 Windows users wanting to look at the source code may have to
277 download and install the free-software
278 @uref{http://www.7-zip.org, 7zip archiver} to extract the tarball.
281 @node Configuring make
282 @section Configuring @command{make}
286 * Running ./autogen.sh::
287 * Running ../configure::
291 @node Running ./autogen.sh
292 @subsection Running @command{./autogen.sh}
294 After you unpack the tarball (or download the Git repository), the
295 contents of your top source directory should be similar to the
296 current source tree listed at
297 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=tree}.
299 Next, you need to create the generated files; enter the following
300 command from your top source directory:
303 ./autogen.sh --noconfigure
306 This will generate a number of files and directories to aid
307 configuration, such as @file{configure}, @file{README.txt}, etc.
309 Next, create the build directory with:
316 We heavily recommend building lilypond inside a separate directory
320 @node Running ../configure
321 @subsection Running @command{../configure}
325 * Configuration options::
326 * Checking build dependencies::
327 * Configuring target directories::
331 @node Configuration options
332 @unnumberedsubsubsec Configuration options
334 @warning{make sure that you are in the @file{build/} subdirectory
335 of your source tree.}
337 The @command{../configure} command (generated by
338 @command{./autogen.sh}) provides many options for configuring
339 @command{make}. To see them all, run:
346 @node Checking build dependencies
347 @unnumberedsubsubsec Checking build dependencies
349 @warning{make sure that you are in the @file{build/} subdirectory
350 of your source tree.}
352 When @command{../configure} is run without any arguments, it will
353 check to make sure your system has everything required for
360 If any build dependency is missing, @command{../configure} will
364 ERROR: Please install required programs: @var{foo}
367 The following message is issued if you are missing programs that
368 are only needed for building the documentation:
371 WARNING: Please consider installing optional programs: @var{bar}
374 If you intend to build the documentation locally, you will need to
375 install or update these programs accordingly.
377 @warning{@command{../configure} may fail to issue warnings for
378 certain documentation build requirements that are not met. If you
379 experience problems when building the documentation, you may need
380 to do a manual check of @ref{Requirements for building
384 @node Configuring target directories
385 @unnumberedsubsubsec Configuring target directories
387 @warning{make sure that you are in the @file{build/} subdirectory
388 of your source tree.}
390 If you intend to use your local build to install a local copy of
391 the program, you will probably want to configure the installation
392 directory. Here are the relevant lines taken from the output of
393 @command{../configure@tie{}--help}:
396 By default, `@command{make@tie{}install}' will install all the
397 files in @file{/usr/local/bin}, @file{/usr/local/lib} etc. You
398 can specify an installation prefix other than @file{/usr/local}
399 using `@option{--prefix}', for instance `@option{--prefix=$HOME}'.
402 A typical installation prefix is @file{$HOME/usr}:
405 ../configure --prefix=$HOME/usr
408 Note that if you plan to install a local build on a system where
409 you do not have root privileges, you will need to do something
410 like this anyway---@command{make@tie{}install} will only succeed
411 if the installation prefix points to a directory where you have
412 write permission (such as your home directory). The installation
413 directory will be automatically created if necessary.
415 The location of the @command{lilypond} command installed by this
416 process will be @file{@var{prefix}/bin/lilypond}; you may want to
417 add @file{@var{prefix}/bin/} to your @code{$PATH} if it is not
420 It is also possible to specify separate installation directories
421 for different types of program files. See the full output of
422 @command{../configure@tie{}--help} for more information.
424 If you encounter any problems, please see @ref{Problems}.
427 @node Compiling LilyPond
428 @section Compiling LilyPond
433 * Saving time with the -j option::
434 * Compiling for multiple platforms::
435 * Useful make variables::
440 @subsection Using @command{make}
442 @warning{make sure that you are in the @file{build/} subdirectory
443 of your source tree.}
445 LilyPond is compiled with the @command{make} command. Assuming
446 @command{make} is configured properly, you can simply run:
452 @samp{make} is short for @samp{make all}. To view a list of @command{make}
459 TODO: Describe what @command{make} actually does.
462 @ref{Generating documentation} provides more info on the @command{make} targets
463 used to build the LilyPond documentation.
466 @node Saving time with the -j option
467 @subsection Saving time with the @option{-j} option
469 If your system has multiple CPUs, you can speed up compilation by
470 adding @samp{-j@var{X}} to the @command{make} command, where
471 @samp{@var{X}} is one more than the number of cores you have. For
472 example, a typical Core2Duo machine would use:
478 If you get errors using the @option{-j} option, and @samp{make}
479 succeeds without it, try lowering the @code{@var{X}} value.
481 Because multiple jobs run in parallel when @option{-j} is used, it can
482 be difficult to determine the source of an error when one occurs. In
483 that case, running @samp{make} without the @option{-j} is advised.
485 @node Compiling for multiple platforms
486 @subsection Compiling for multiple platforms
488 If you want to build multiple versions of LilyPond with different
489 configuration settings, you can use the
490 @option{--enable-config=@var{conf}} option of @command{configure}.
491 You should use @code{make@tie{}conf=@var{conf}} to generate the
492 output in @file{out-@var{conf}}. For example, suppose you want to
493 build with and without profiling, then use the following for the
497 ./configure --prefix=$HOME/usr/ --enable-checking
501 and for the profiling version, specify a different configuration
504 ./configure --prefix=$HOME/usr/ --enable-profiling \
505 --enable-config=prof --disable-checking
509 If you wish to install a copy of the build with profiling, don't
510 forget to use @code{conf=@var{CONF}} when issuing
511 @command{make@tie{}install}:
514 make conf=prof install
519 @ref{Installing LilyPond from a local build}
522 @node Useful make variables
523 @subsection Useful @command{make} variables
525 If a less verbose build output if desired, the variable
526 @code{QUIET_BUILD} may be set to @code{1} on @command{make}
527 command line, or in @file{local.make} at top of the build tree.
530 @node Post-compilation options
531 @section Post-compilation options
535 * Installing LilyPond from a local build::
536 * Generating documentation::
537 * Testing LilyPond binary::
541 @node Installing LilyPond from a local build
542 @subsection Installing LilyPond from a local build
544 If you configured @command{make} to install your local build in a
545 directory where you normally have write permission (such as your
546 home directory), and you have compiled LilyPond by running
547 @command{make}, you can install the program in your target
548 directory by running:
554 If instead, your installation directory is not one that you can
555 normally write to (such as the default @file{/usr/local/}, which
556 typically is only writeable by the superuser), you will need to
557 temporarily become the superuser when running
558 @command{make@tie{}install}:
571 If you don't have superuser privileges, then you need to configure
572 the installation directory to one that you can write to, and then
573 re-install. See @ref{Configuring target directories}.
576 @node Generating documentation
577 @subsection Generating documentation
581 * Documentation editor's edit/compile cycle::
582 * Building documentation::
583 * Building a single document::
584 * Saving time with CPU_COUNT::
586 * Installing documentation::
587 * Building documentation without compiling::
591 @node Documentation editor's edit/compile cycle
592 @unnumberedsubsubsec Documentation editor's edit/compile cycle
596 Initial documentation build:
600 make [-j@var{X} CPU_COUNT=@var{X}] doc @emph{## can take an hour or more}
601 make [-j@var{X} CPU_COUNT=@var{X}] doc-stage-1 @emph{## to build only PDF documentation}
608 @emph{## edit source files, then...}
610 make [-j@var{X}] @emph{## needed if editing outside}
611 @emph{## Documentation/, but useful anyway}
612 @emph{## for finding Texinfo errors.}
613 make [-j@var{X} CPU_COUNT=@var{X}] doc @emph{## usually faster than initial build.}
619 In some cases, it is possible to clean the compiled documentation
620 with @samp{make@tie{}doc-clean}, but this method is not guaranteed
621 to fix everything. Instead, we recommend that you delete your
622 @file{build/} directory, and begin compiling from scratch. Since
623 the documentation compile takes much longer than the
624 non-documentation compile, this does not increase the overall time
629 @node Building documentation
630 @unnumberedsubsubsec Building documentation
632 After a successful compile (using @command{make}), the
633 documentation can be built by issuing:
639 or, to build only the PDF documentation and not the HTML,
645 @warning{The first time you run @command{make@tie{}doc}, the
646 process can easily take an hour or more with not much output
647 on the command line.}
649 After this initial build, @command{make@tie{}doc} only makes
650 changes to the documentation where needed, so it may only take
651 a minute or two to test changes if the documentation is already
654 If @command{make@tie{}doc} succeeds, the HTML documentation tree
655 is available in @file{out-www/offline-root/}, and can be browsed
656 locally. Various portions of the documentation can be found by
657 looking in @file{out/} and @file{out-www} subdirectories in other
658 places in the source tree, but these are only @emph{portions} of
659 the docs. Please do not complain about anything which is broken
660 in those places; the only complete set of documentation is in
661 @file{out-www/offline-root/} from the top of the source tree.
663 @code{make doc} compiles the documents for all languages. To save
664 some compile time, the English language documents can be compiled
671 @noindent Similarly, it is possible to compile a subset of the
672 translated documentation by specifying their language codes on the
673 command line. For example, the French and German translations are
677 make LANGS='de fr' doc
680 @noindent Note that this will also compile the English version.
682 Compilation of documentation in Info format with images can be
683 done separately by issuing:
690 An issue when switching branches between master and translation
691 is the appearance/disappearance of translated versions of some manuals.
692 If you see such a warning from make:
695 No rule to make target `X', needed by `Y'
699 Your best bet is to delete the file Y.dep and to try again.
701 @node Building a single document
702 @unnumberedsubsubsec Building a single document
703 It's possible to build a single document. For example, to rebuild
704 only @file{contributor.pdf}, do the following:
709 touch ../../Documentation/contributor.texi
710 make out=www out-www/contributor.pdf
713 If you are only working on a single document, test-building it in
714 this way can give substantial time savings - recreating
715 @file{contributor.pdf}, for example, takes a matter of seconds.
717 @node Saving time with CPU_COUNT
718 @unnumberedsubsubsec Saving time with @code{CPU_COUNT}
720 The most time consuming task for building the documentation is
721 running LilyPond to build images of music, and there cannot be
722 several simultaneously running @command{lilypond-book} instances,
723 so the @option{-j} @command{make} option does not significantly
724 speed up the build process. To help speed it up, the makefile
725 variable @option{CPU_COUNT} may be set in @file{local.make} or on
726 the command line to the number of @code{.ly} files that LilyPond
727 should process simultaneously, e.g. on a bi-processor or dual core
731 make -j3 CPU_COUNT=3 doc
735 The recommended value of @option{CPU_COUNT} is one plus the number
736 of cores or processors, but it is advisable to set it to a smaller
737 value unless your system has enough RAM to run that many
738 simultaneous LilyPond instances. Also, values for the @option{-j}
739 option that pose problems with @samp{make} are less likely to pose
740 problems with @samp{make doc} (this applies to both @option{-j}
741 and @option{CPU_COUNT}). For example, with a quad-core processor,
742 it is possible for @samp{make -j5 CPU_COUNT=5 doc} to work
743 consistently even if @samp{make -j5} rarely succeeds.
747 @unnumberedsubsubsec AJAX search
749 To build the documentation with interactive searching, use:
752 make doc AJAX_SEARCH=1
755 This requires PHP, and you must view the docs via a http
756 connection (you cannot view them on your local filesystem).
758 @warning{Due to potential security or load issues, this option is
759 not enabled in the official documentation builds. Enable at your
763 @node Installing documentation
764 @unnumberedsubsubsec Installing documentation
766 The HTML, PDF and if available Info files can be installed into
767 the standard documentation path by issuing
774 This also installs Info documentation with images if the
775 installation prefix is properly set; otherwise, instructions to
776 complete proper installation of Info documentation are printed on
779 To install the Info documentation separately, run:
786 Note that to get the images in Info documentation, @code{install-doc}
787 target creates symbolic links to HTML and PDF installed documentation
788 tree in @file{@var{prefix}/share/info}, in order to save disk space,
789 whereas @code{install-info} copies images in
790 @file{@var{prefix}/share/info} subdirectories.
792 It is possible to build a documentation tree in
793 @file{out-www/online-root/}, with special processing, so it can be
794 used on a website with content negotiation for automatic language
795 selection; this can be achieved by issuing
798 make WEB_TARGETS=online doc
802 and both @q{offline} and @q{online} targets can be generated by issuing
805 make WEB_TARGETS="offline online" doc
808 Several targets are available to clean the documentation build and
809 help with maintaining documentation; an overview of these targets is
817 from every directory in the build tree. Most targets for
818 documentation maintenance are available from
819 @file{Documentation/}; for more information, see
820 @rcontrib{Documentation work}.
822 The makefile variable @code{QUIET_BUILD} may be set to @code{1}
823 for a less verbose build output, just like for building the
827 @node Building documentation without compiling
828 @unnumberedsubsubsec Building documentation without compiling
831 The documentation can be built locally without compiling LilyPond
832 binary, if LilyPond is already installed on your system.
834 From a fresh Git checkout, do
837 ./autogen.sh # ignore any warning messages
838 cp GNUmakefile.in GNUmakefile
839 make -C scripts && make -C python
840 nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond doc
843 Please note that this may break sometimes -- for example, if a new
844 feature is added with a test file in input/regression, even the latest
845 development release of LilyPond will fail to build the docs.
847 You may build the manual without building all the @file{input/*} stuff
848 (i.e. mostly regression tests): change directory, for example to
849 @file{Documentation/}, issue @code{make doc}, which will build
850 documentation in a subdirectory @file{out-www} from the source files in
851 current directory. In this case, if you also want to browse the
852 documentation in its post-processed form, change back to top directory
856 make out=www WWW-post
861 You may also need to create a script for @command{pngtopnm} and
862 @code{pnmtopng}. On GNU/Linux, I use this:
865 export LD_LIBRARY_PATH=/usr/lib
866 exec /usr/bin/pngtopnm "$@"
869 On MacOS X with fink, I use this:
872 export DYLD_LIBRARY_PATH=/sw/lib
873 exec /sw/bin/pngtopnm "$@"
876 On MacOS X with macports, you should use this:
879 export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib
880 exec /opt/local/bin/pngtopnm "$@"
884 @node Testing LilyPond binary
885 @subsection Testing LilyPond binary
888 LilyPond comes with an extensive suite that exercises the entire
889 program. This suite can be used to test that the binary has
890 been built correctly.
892 The test suite can be executed with:
898 If the test suite completes successfully, the LilyPond binary
901 More information on the regression test suite is found at
902 @rcontrib{Regression tests}.
907 For help and questions use @email{lilypond-user@@gnu.org}. Send
908 bug reports to @email{bug-lilypond@@gnu.org}.
910 Bugs that are not fault of LilyPond are documented here.
912 @unnumberedsubsubsec Bison 1.875
914 There is a bug in bison-1.875: compilation fails with "parse error
915 before `goto'" in line 4922 due to a bug in bison. To fix, please
916 recompile bison 1.875 with the following fix
919 $ cd lily; make out/parser.cc
920 $ vi +4919 out/parser.cc
921 # append a semicolon to the line containing "__attribute__ ((__unused__))
927 @unnumberedsubsubsec Compiling on MacOS@tie{}X
929 Here are special instructions for compiling under MacOS@tie{}X.
930 These instructions assume that dependencies are installed using
931 @uref{http://www.macports.org/, MacPorts.} The instructions have
932 been tested using OS X 10.5 (Leopard).
934 First, install the relevant dependencies using MacPorts.
936 Next, add the following to your relevant shell initialization
937 files. This is @code{~/.profile} by default. You should create
938 this file if it does not exist.
941 export PATH=/opt/local/bin:/opt/local/sbin:$PATH
942 export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:$DYLD_FALLBACK_LIBRARY_PATH
945 Now you must edit the generated @file{config.make} file. Change
948 FLEXLEXER_FILE = /usr/include/FlexLexer.h
955 FLEXLEXER_FILE = /opt/local/include/FlexLexer.h
958 At this point, you should verify that you have the appropriate
959 fonts installed with your ghostscript installation. Check @code{ls
960 /opt/local/share/ghostscript/fonts} for: 'c0590*' files (.pfb,
961 .pfb and .afm). If you don't have them, run the following
962 commands to grab them from the ghostscript SVN server and install
963 them in the appropriate location:
966 svn export http://svn.ghostscript.com/ghostscript/tags/urw-fonts-1.0.7pre44/
967 sudo mv urw-fonts-1.0.7pre44/* /opt/local/share/ghostscript/fonts/
968 rm -rf urw-fonts-1.07pre44
971 Now run the @code{./configure} script. To avoid complications with
972 automatic font detection, add
975 --with-ncsb-dir=/opt/local/share/ghostscript/fonts
979 @unnumberedsubsubsec Solaris
981 Solaris7, ./configure
983 @file{./configure} needs a POSIX compliant shell. On Solaris7,
984 @file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash
985 is. Run configure like
988 CONFIG_SHELL=/bin/ksh ksh -c ./configure
995 CONFIG_SHELL=/bin/bash bash -c ./configure
998 @unnumberedsubsubsec FreeBSD
1000 To use system fonts, dejaview must be installed. With the default
1001 port, the fonts are installed in @file{usr/X11R6/lib/X11/fonts/dejavu}.
1003 Open the file @file{$LILYPONDBASE/usr/etc/fonts/local.conf} and add the
1004 following line just after the @code{<fontconfig>} line. (Adjust as necessary
1005 for your hierarchy.)
1008 <dir>/usr/X11R6/lib/X11/fonts</dir>
1012 @unnumberedsubsubsec International fonts
1014 On Mac OS X, all fonts are installed by default. However, finding all
1015 system fonts requires a bit of configuration; see
1016 @uref{http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html,
1017 this post} on the @code{lilypond-user} mailing list.
1019 On Linux, international fonts are installed by different means on
1020 every distribution. We cannot list the exact commands or packages
1021 that are necessary, as each distribution is different, and the exact
1022 package names within each distribution changes. Here are some
1028 taipeifonts fonts-xorg-truetype ttfonts-ja fonts-arabic \
1029 ttfonts-zh_CN fonts-ja fonts-hebrew
1033 apt-get install emacs-intl-fonts xfonts-intl-.* \
1034 ttf-kochi-gothic ttf-kochi-mincho \
1035 xfonts-bolkhov-75dpi xfonts-cronyx-100dpi xfonts-cronyx-75dpi
1039 @unnumberedsubsubsec Using lilypond python libraries
1041 If you want to use lilypond's python libraries (either running
1042 certain build scripts manually, or using them in other programs),
1043 set @code{PYTHONPATH} to @file{python/out} in your build
1044 directory, or @file{.../usr/lib/lilypond/current/python} in the
1045 installation directory structure.
1050 @node Concurrent stable and development versions
1051 @section Concurrent stable and development versions
1054 It can be useful to have both the stable and the development versions
1055 of Lilypond available at once. One way to do this on GNU/Linux is to
1056 install the stable version using the precompiled binary, and run the
1057 development version from the source tree. After running @command{make
1058 all} from the top directory of the Lilypond source files, there will
1059 be a binary called @code{lilypond} in the @code{out} directory:
1062 <@var{path to}>/lilypond/out/bin/lilypond
1065 This binary can be run without actually doing the @code{make
1066 install} command. The advantage to this is that you can have all
1067 of the latest changes available after pulling from git and running
1068 @code{make all}, without having to uninstall the old version and
1071 So, to use the stable version, install it as usual and use the
1078 To use the development version, create a link to the binary in the
1079 source tree by saving the following line in a file somewhere in your
1083 exec <@var{path to}>/lilypond/out/bin/lilypond "$@@"
1086 Save it as @code{Lilypond} (with a capital L to distinguish it
1087 from the stable @code{lilypond}), and make it executable:
1093 Then you can invoke the development version this way:
1102 - other compilation tricks for developers
1106 @section Build system
1109 We currently use make and stepmake, which is complicated and only
1110 used by us. Hopefully this will change in the future.
1113 @subsubheading Version-specific texinfo macros
1118 made with @command{scripts/build/create-version-itexi.py} and@*
1119 @command{scripts/build/create-weblinks-itexi.py}
1122 used extensively in the @code{WEBSITE_ONLY_BUILD} version of the
1123 website (made with @file{website.make}, used on lilypond.org)
1126 not (?) used in the main docs?
1129 the numbers in VERSION file: MINOR_VERSION should be 1 more than
1130 the last release, VERSION_DEVEL should be the last @strong{online}
1131 release. Yes, VERSION_DEVEL is less than VERSION.