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 `@code{--prefix}', for instance `@code{--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 @node Saving time with the -j option
463 @subsection Saving time with the @option{-j} option
465 If your system has multiple CPUs, you can speed up compilation by
466 adding @samp{-j@var{X}} to the @command{make} command, where
467 @samp{@var{X}} is one more than the number of cores you have. For
468 example, a typical Core2Duo machine would use:
474 If you get errors using the @option{-j} option, and @samp{make}
475 succeeds without it, try lowering the @code{@var{X}} value.
477 Because multiple jobs run in parallel when @option{-j} is used, it can
478 be difficult to determine the source of an error when one occurs. In
479 that case, running @samp{make} without the @option{-j} is advised.
481 @node Compiling for multiple platforms
482 @subsection Compiling for multiple platforms
484 If you want to build multiple versions of LilyPond with different
485 configuration settings, you can use the
486 @code{--enable-config=@var{CONF}} option of @command{configure}.
487 You should use @code{make@tie{}conf=@var{CONF}} to generate the
488 output in @file{out-@var{CONF}}. For example, suppose you want to
489 build with and without profiling, then use the following for the
493 ./configure --prefix=$HOME/usr/ --enable-checking
497 and for the profiling version, specify a different configuration
500 ./configure --prefix=$HOME/usr/ --enable-profiling \
501 --enable-config=prof --disable-checking
505 If you wish to install a copy of the build with profiling, don't
506 forget to use @code{conf=@var{CONF}} when issuing
507 @command{make@tie{}install}:
510 make conf=prof install
515 @ref{Installing LilyPond from a local build}
518 @node Useful make variables
519 @subsection Useful @command{make} variables
521 If a less verbose build output if desired, the variable
522 @code{QUIET_BUILD} may be set to @code{1} on @command{make}
523 command line, or in @file{local.make} at top of the build tree.
526 @node Post-compilation options
527 @section Post-compilation options
531 * Installing LilyPond from a local build::
532 * Generating documentation::
533 * Testing LilyPond binary::
537 @node Installing LilyPond from a local build
538 @subsection Installing LilyPond from a local build
540 If you configured @command{make} to install your local build in a
541 directory where you normally have write permission (such as your
542 home directory), and you have compiled LilyPond by running
543 @command{make}, you can install the program in your target
544 directory by running:
550 If instead, your installation directory is not one that you can
551 normally write to (such as the default @file{/usr/local/}, which
552 typically is only writeable by the superuser), you will need to
553 temporarily become the superuser when running
554 @command{make@tie{}install}:
567 If you don't have superuser privileges, then you need to configure
568 the installation directory to one that you can write to, and then
569 re-install. See @ref{Configuring target directories}.
572 @node Generating documentation
573 @subsection Generating documentation
577 * Documentation editor's edit/compile cycle::
578 * Building documentation::
579 * Saving time with CPU_COUNT::
581 * Installing documentation::
582 * Building documentation without compiling::
586 @node Documentation editor's edit/compile cycle
587 @unnumberedsubsubsec Documentation editor's edit/compile cycle
591 Initial documentation build:
595 make [-j@var{X} CPU_COUNT=@var{X}] doc @emph{## can take an hour or more}
602 @emph{## edit source files, then...}
604 make [-j@var{X}] @emph{## needed if editing outside}
605 @emph{## Documentation/, but useful anyway}
606 @emph{## for finding Texinfo errors.}
607 touch Documentation/*te?? @emph{## bug workaround}
608 make [-j@var{X} CPU_COUNT=@var{X}] doc @emph{## usually faster than initial build.}
614 In some cases, it is possible to clean the compiled documentation
615 with @samp{make@tie{}doc-clean}, but this method is not guaranteed
616 to fix everything. Instead, we recommend that you delete your
617 @file{build/} directory, and begin compiling from scratch. Since
618 the documentation compile takes much longer than the
619 non-documentation compile, this does not increase the overall time
624 @node Building documentation
625 @unnumberedsubsubsec Building documentation
627 After a successful compile (using @command{make}), the
628 documentation can be built by issuing:
634 The first time you run @command{make@tie{}doc}, the process can
635 easily take an hour or more. After that, @command{make@tie{}doc}
636 only makes changes to the pre-built documentation where needed,
637 so it may only take a minute or two to test changes if the
638 documentation is already built.
640 If @command{make@tie{}doc} succeeds, the HTML documentation tree
641 is available in @file{out-www/offline-root/}, and can be browsed
642 locally. Various portions of the documentation can be found by
643 looking in @file{out/} and @file{out-www} subdirectories in other
644 places in the source tree, but these are only @emph{portions} of
645 the docs. Please do not complain about anything which is broken
646 in those places; the only complete set of documentation is in
647 @file{out-www/offline-root/} from the top of the source tree.
649 Compilation of documentation in Info format with images can be
650 done separately by issuing:
658 If source files have changed since the last documentation build,
659 output files that need to be rebuilt are normally rebuilt, even if
660 you do not run @code{make@tie{}doc-clean} first. However, build
661 dependencies in the documentation are so complex that some
662 newly-edited files may not be rebuilt as they should be; a
663 workaround is to @command{touch} the top source file for any
664 manual you've edited. For example, if you make changes to a file
665 in @file{notation/}, do:
668 touch Documentation/notation.tely
672 The top sources possibly affected by this are:
675 Documentation/extend.texi
676 Documentation/changes.tely
677 Documentation/contributor.texi
678 Documentation/essay.tely
679 Documentation/extending.tely
680 Documentation/learning.tely
681 Documentation/notation.tely
682 Documentation/snippets.tely
683 Documentation/usage.tely
684 Documentation/web.texi
688 You can @command{touch} all of them at once with:
691 touch Documentation/*te??
695 However, this will rebuild all of the manuals
696 indiscriminately---it is more efficient to @command{touch} only
700 @node Saving time with CPU_COUNT
701 @unnumberedsubsubsec Saving time with @code{CPU_COUNT}
703 The most time consuming task for building the documentation is
704 running LilyPond to build images of music, and there cannot be
705 several simultaneously running @command{lilypond-book} instances,
706 so the @option{-j} @command{make} option does not significantly
707 speed up the build process. To help speed it up, the makefile
708 variable @option{CPU_COUNT} may be set in @file{local.make} or on
709 the command line to the number of @code{.ly} files that LilyPond
710 should process simultaneously, e.g. on a bi-processor or dual core
714 make -j3 CPU_COUNT=3 doc
718 The recommended value of @option{CPU_COUNT} is one plus the number
719 of cores or processors, but it is advisable to set it to a smaller
720 value unless your system has enough RAM to run that many
721 simultaneous LilyPond instances. Also, values for the @option{-j}
722 option that pose problems with @samp{make} are less likely to pose
723 problems with @samp{make doc} (this applies to both @option{-j}
724 and @option{CPU_COUNT}). For example, with a quad-core processor,
725 it is possible for @samp{make -j5 CPU_COUNT=5 doc} to work
726 consistently even if @samp{make -j5} rarely succeeds.
730 @unnumberedsubsubsec AJAX search
732 To build the documentation with interactive searching, use:
735 make doc AJAX_SEARCH=1
738 This requires PHP, and you must view the docs via a http
739 connection (you cannot view them on your local filesystem).
741 @warning{Due to potential security or load issues, this option is
742 not enabled in the official documentation builds. Enable at your
746 @node Installing documentation
747 @unnumberedsubsubsec Installing documentation
749 The HTML, PDF and if available Info files can be installed into
750 the standard documentation path by issuing
757 This also installs Info documentation with images if the
758 installation prefix is properly set; otherwise, instructions to
759 complete proper installation of Info documentation are printed on
762 To install the Info documentation separately, run:
769 Note that to get the images in Info documentation, @code{install-doc}
770 target creates symbolic links to HTML and PDF installed documentation
771 tree in @file{@var{prefix}/share/info}, in order to save disk space,
772 whereas @code{install-info} copies images in
773 @file{@var{prefix}/share/info} subdirectories.
775 It is possible to build a documentation tree in
776 @file{out-www/online-root/}, with special processing, so it can be
777 used on a website with content negotiation for automatic language
778 selection; this can be achieved by issuing
781 make WEB_TARGETS=online doc
785 and both @q{offline} and @q{online} targets can be generated by issuing
788 make WEB_TARGETS="offline online" doc
791 Several targets are available to clean the documentation build and
792 help with maintaining documentation; an overview of these targets is
800 from every directory in the build tree. Most targets for
801 documentation maintenance are available from
802 @file{Documentation/}; for more information, see
803 @rcontrib{Documentation work}.
805 The makefile variable @code{QUIET_BUILD} may be set to @code{1}
806 for a less verbose build output, just like for building the
810 @node Building documentation without compiling
811 @unnumberedsubsubsec Building documentation without compiling
814 The documentation can be built locally without compiling LilyPond
815 binary, if LilyPond is already installed on your system.
817 From a fresh Git checkout, do
820 ./autogen.sh # ignore any warning messages
821 cp GNUmakefile.in GNUmakefile
822 make -C scripts && make -C python
823 nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond doc
826 Please note that this may break sometimes -- for example, if a new
827 feature is added with a test file in input/regression, even the latest
828 development release of LilyPond will fail to build the docs.
830 You may build the manual without building all the @file{input/*} stuff
831 (i.e. mostly regression tests): change directory, for example to
832 @file{Documentation/}, issue @code{make doc}, which will build
833 documentation in a subdirectory @file{out-www} from the source files in
834 current directory. In this case, if you also want to browse the
835 documentation in its post-processed form, change back to top directory
839 make out=www WWW-post
844 You may also need to create a script for @command{pngtopnm} and
845 @code{pnmtopng}. On GNU/Linux, I use this:
848 export LD_LIBRARY_PATH=/usr/lib
849 exec /usr/bin/pngtopnm "$@"
852 On MacOS X with fink, I use this:
855 export DYLD_LIBRARY_PATH=/sw/lib
856 exec /sw/bin/pngtopnm "$@"
859 On MacOS X with macports, you should use this:
862 export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib
863 exec /opt/local/bin/pngtopnm "$@"
867 @node Testing LilyPond binary
868 @subsection Testing LilyPond binary
871 LilyPond comes with an extensive suite that exercises the entire
872 program. This suite can be used to test that the binary has
873 been built correctly.
875 The test suite can be executed with:
881 If the test suite completes successfully, the LilyPond binary
884 More information on the regression test suite is found at
885 @rcontrib{Regression tests}.
890 For help and questions use @email{lilypond-user@@gnu.org}. Send
891 bug reports to @email{bug-lilypond@@gnu.org}.
893 Bugs that are not fault of LilyPond are documented here.
895 @unnumberedsubsubsec Bison 1.875
897 There is a bug in bison-1.875: compilation fails with "parse error
898 before `goto'" in line 4922 due to a bug in bison. To fix, please
899 recompile bison 1.875 with the following fix
902 $ cd lily; make out/parser.cc
903 $ vi +4919 out/parser.cc
904 # append a semicolon to the line containing "__attribute__ ((__unused__))
910 @unnumberedsubsubsec Compiling on MacOS@tie{}X
912 Here are special instructions for compiling under MacOS@tie{}X.
913 These instructions assume that dependencies are installed using
914 @uref{http://www.macports.org/, MacPorts.} The instructions have
915 been tested using OS X 10.5 (Leopard).
917 First, install the relevant dependencies using MacPorts.
919 Next, add the following to your relevant shell initialization
920 files. This is @code{~/.profile} by default. You should create
921 this file if it does not exist.
924 export PATH=/opt/local/bin:/opt/local/sbin:$PATH
925 export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:$DYLD_FALLBACK_LIBRARY_PATH
928 Now you must edit the generated @file{config.make} file. Change
931 FLEXLEXER_FILE = /usr/include/FlexLexer.h
938 FLEXLEXER_FILE = /opt/local/include/FlexLexer.h
941 At this point, you should verify that you have the appropriate
942 fonts installed with your ghostscript installation. Check @code{ls
943 /opt/local/share/ghostscript/fonts} for: 'c0590*' files (.pfb,
944 .pfb and .afm). If you don't have them, run the following
945 commands to grab them from the ghostscript SVN server and install
946 them in the appropriate location:
949 svn export http://svn.ghostscript.com/ghostscript/tags/urw-fonts-1.0.7pre44/
950 sudo mv urw-fonts-1.0.7pre44/* /opt/local/share/ghostscript/fonts/
951 rm -rf urw-fonts-1.07pre44
954 Now run the @code{./configure} script. To avoid complications with
955 automatic font detection, add
958 --with-ncsb-dir=/opt/local/share/ghostscript/fonts
962 @unnumberedsubsubsec Solaris
964 Solaris7, ./configure
966 @file{./configure} needs a POSIX compliant shell. On Solaris7,
967 @file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash
968 is. Run configure like
971 CONFIG_SHELL=/bin/ksh ksh -c ./configure
978 CONFIG_SHELL=/bin/bash bash -c ./configure
981 @unnumberedsubsubsec FreeBSD
983 To use system fonts, dejaview must be installed. With the default
984 port, the fonts are installed in @file{usr/X11R6/lib/X11/fonts/dejavu}.
986 Open the file @file{$LILYPONDBASE/usr/etc/fonts/local.conf} and add the
987 following line just after the @code{<fontconfig>} line. (Adjust as necessary
991 <dir>/usr/X11R6/lib/X11/fonts</dir>
995 @unnumberedsubsubsec International fonts
997 On Mac OS X, all fonts are installed by default. However, finding all
998 system fonts requires a bit of configuration; see
999 @uref{http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html,
1000 this post} on the @code{lilypond-user} mailing list.
1002 On Linux, international fonts are installed by different means on
1003 every distribution. We cannot list the exact commands or packages
1004 that are necessary, as each distribution is different, and the exact
1005 package names within each distribution changes. Here are some
1011 taipeifonts fonts-xorg-truetype ttfonts-ja fonts-arabic \
1012 ttfonts-zh_CN fonts-ja fonts-hebrew
1016 apt-get install emacs-intl-fonts xfonts-intl-.* \
1017 ttf-kochi-gothic ttf-kochi-mincho \
1018 xfonts-bolkhov-75dpi xfonts-cronyx-100dpi xfonts-cronyx-75dpi
1022 @unnumberedsubsubsec Using lilypond python libraries
1024 If you want to use lilypond's python libraries (either running
1025 certain build scripts manually, or using them in other programs),
1026 set @code{PYTHONPATH} to @file{python/out} in your build
1027 directory, or @file{.../usr/lib/lilypond/current/python} in the
1028 installation directory structure.
1033 @node Concurrent stable and development versions
1034 @section Concurrent stable and development versions
1037 It can be useful to have both the stable and the development versions
1038 of Lilypond available at once. One way to do this on GNU/Linux is to
1039 install the stable version using the precompiled binary, and run the
1040 development version from the source tree. After running @command{make
1041 all} from the top directory of the Lilypond source files, there will
1042 be a binary called @code{lilypond} in the @code{out} directory:
1045 <@var{path to}>/lilypond/out/bin/lilypond
1048 This binary can be run without actually doing the @code{make
1049 install} command. The advantage to this is that you can have all
1050 of the latest changes available after pulling from git and running
1051 @code{make all}, without having to uninstall the old version and
1054 So, to use the stable version, install it as usual and use the
1061 To use the development version, create a link to the binary in the
1062 source tree by saving the following line in a file somewhere in your
1066 exec <@var{path to}>/lilypond/out/bin/lilypond "$@@"
1069 Save it as @code{Lilypond} (with a capital L to distinguish it
1070 from the stable @code{lilypond}), and make it executable:
1076 Then you can invoke the development version this way:
1085 - other compilation tricks for developers
1089 @section Build system
1092 We currently use make and stepmake, which is complicated and only
1093 used by us. Hopefully this will change in the future.
1096 @subsubheading Version-specific texinfo macros
1101 made with @command{scripts/build/create-version-itexi.py} and@*
1102 @command{scripts/build/create-weblinks-itexi.py}
1105 used extensively in the @code{WEBSITE_ONLY_BUILD} version of the
1106 website (made with @file{website.make}, used on lilypond.org)
1109 not (?) used in the main docs?
1112 the numbers in VERSION file: MINOR_VERSION should be 1 more than
1113 the last release, VERSION_DEVEL should be the last @strong{online}
1114 release. Yes, VERSION_DEVEL is less than VERSION.