-x T ascii
-x res 240 24 40
-x init
-p1
-x font 3 B
-f3
-s10
-V400
-H144
-tINSTALL
-wh24
-t-
-wh24
-tcompiling
-wh24
-tand
-wh24
-tinstalling
-wh24
-tGNU
-wh24
-tLilyPond
-n40 0
-x font 2 I
-f2
-V480
-H600
-tHWN
-wh24
-t&
-wh24
-tJCN
-n40 0
-f3
-V600
-H0
-tContents
-n40 0
-x font 1 R
-f1
-V680
-H120
-t1:
-wh24
-tABSTRACT
-n40 0
-V720
-H0
-t2:
-wh24
-tOBTAINING
-n40 0
-V760
-H0
-t3:
-wh24
-tPREREQUISITES
-n40 0
-V800
-H0
-t4:
-wh24
-tRUNNING
-n40 0
-V840
-H0
-t5:
-wh24
-tWEBSITE
-n40 0
-V880
-H0
-t6:
-wh24
-tCONFIGURING
-wh24
-tand
-wh24
-tCOMPILING
-n40 0
-V920
-H0
-t7:
-wh24
-tCONFIGURING
-wh24
-tFOR
-wh24
-tMULTIPLE
-wh24
-tPLATFORMS
-n40 0
-V960
-H0
-t8:
-wh24
-tINSTALLING
-n40 0
-V1000
-H0
-t9:
-wh24
-tREDHAT
-wh24
-tLINUX
-n40 0
-V1040
-H0
-t10:
-wh24
-tDEBIAN
-wh24
-tGNU/LINUX
-n40 0
-V1080
-H0
-t11:
-wh24
-tWINDOWS
-wh24
-tNT/95
-n40 0
-V1120
-H0
-t12:
-wh24
-tAUTHORS
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p2
-x font 1 R
-f1
-s10
-V160
-H696
-t-2-
-h672
-n40 0
-x font 3 B
-f3
-V280
-H0
-t1:
-wh24
-tABSTRACT
-n40 0
-f1
-V400
-H0
-tThis
-wh48
-tdocument
-wh48
-texplains
-wh48
-twhat
-wh24
-tyou
-wh24
-tneed
-wh24
-tto
-wh24
-tinstall
-wh24
-tLilyPond,
-n40 0
-V440
-H0
-tand
-wh24
-twhat
-wh24
-tyou
-wh24
-tshould
-wh24
-tdo.
-wh48
-tIf
-wh24
-tyou
-wh24
-tare
-wh48
-tgoing
-wh48
-tto
-wh48
-tcompile
-wh48
-tand
-n40 0
-V480
-H0
-tinstall
-wh48
-tLilyPond
-wh48
-toften,
-wh48
-te.g.
-wh48
-twhen
-wh24
-tdoing
-wh24
-tdevelopment,
-wh24
-tyou
-n40 0
-V520
-H0
-tmight
-wh24
-twant
-wh24
-tto
-wh24
-tcheck
-wh24
-tout
-wh24
-tthe
-wf3
-h24
-tbuildscripts/set-lily.sh
-wf1
-h24
-tscript.
-n40 0
-V560
-H0
-tIt
-wh24
-tsets
-wh24
-tsome
-wh24
-tenvironment
-wh24
-tvariables
-wh24
-tand
-wh24
-tsymlinks,
-wh24
-twhich
-wh24
-tcomes
-n40 0
-V600
-H0
-tin
-wh24
-thandly
-wh24
-twhen
-wh24
-tyou
-wh24
-thave
-wh24
-tto
-wh24
-tcompile
-wh24
-tLilyPond
-wh24
-tmore
-wh24
-toften.
-n40 0
-f3
-V720
-H0
-t2:
-wh24
-tOBTAINING
-n40 0
-f1
-V840
-H0
-tYou
-wh48
-tcan
-wh72
-tget
-wh72
-tthe
-wh72
-tlatest
-wh72
-tversion
-wh72
-tof
-wh72
-tLilyPond
-wh72
-tat
-n40 0
-V880
-H0
-tftp://ftp.cs.uu.nl/pub/GNU/LilyPond/.
-wh72
-tRefer
-wh48
-tto
-wh48
-tthe
-wh24
-tlinks
-n40 0
-V920
-H0
-tdocument
-wh24
-tfor
-wh24
-tmirror
-wh24
-tsites.
-n40 0
-x font 2 I
-f2
-V1000
-H0
-tIf
-wh24
-tyou
-wh24
-tupgrade
-wh24
-tby
-wh24
-tpatching
-wh24
-tdo
-wh48
-tremember
-wh48
-tto
-wh48
-trerun
-wh48
-tautoconf
-n40 0
-V1040
-H0
-tafter
-wh24
-tapplying
-wh24
-tthe
-wh24
-tpatch
-f1
-t.
-n40 0
-f3
-V1160
-H0
-t3:
-wh24
-tPREREQUISITES
-n40 0
-f1
-V1280
-H0
-tFor
-wh24
-tcompilation
-wh24
-tyou
-wh24
-tneed:
-n40 0
-V1400
-H0
-to
-h96
-tA
-wh24
-tGNU
-wh24
-tsystem:
-wh24
-tGNU
-wh24
-tLilyPond
-wh24
-tis
-wh24
-tknown
-wh24
-tto
-wh24
-trun
-wh24
-ton
-wh24
-tthese
-wh24
-tGNU
-n40 0
-V1440
-H120
-tsystems:
-wh24
-tLinux
-wh24
-t(PPC,
-wh24
-tintel),
-wh48
-tFreeBSD,
-wh48
-tAIX,
-wh48
-tNeXTStep,
-n40 0
-V1480
-H120
-tIRIX,
-wh24
-tDigital
-wh24
-tUnix
-wh24
-tand
-wh24
-tSolaris.
-n40 0
-V1600
-H0
-to
-h96
-tLots
-wh48
-tof
-wh48
-tdisk
-wh24
-tspace:
-wh24
-tLilyPond
-wh24
-ttakes
-wh24
-tbetween
-wh24
-t30
-wh24
-tand
-wh24
-t100
-n40 0
-V1640
-H120
-tmb
-wh24
-tto
-wh24
-tcompile
-wh24
-tif
-wh24
-tyou
-wh24
-tuse
-wh24
-tdebugging
-wh24
-tinformation.
-wh48
-tIf
-wh24
-tyou
-n40 0
-V1680
-H120
-tare
-wh48
-tshort
-wh48
-ton
-wh24
-tdisk-space
-wh24
-trun
-wh24
-tconfigure
-wh24
-twith
-wh24
-t--disable-
-n40 0
-V1720
-H120
-tdebugging.
-n40 0
-V1800
-H120
-tAlthough
-wh24
-twe
-wh24
-trecommend
-wh24
-tto
-wh24
-tuse
-wh24
-tUnix,
-wh24
-tLilyPond
-wh24
-tis
-wh24
-tknown
-wh24
-tto
-n40 0
-V1840
-H120
-trun
-wh24
-ton
-wh24
-tWindows
-wh24
-tNT/95/98
-wh24
-tas
-wh24
-twell.
-wh48
-tSee
-wh24
-tSection
-wh24
-t11.
-n40 0
-V1960
-H0
-to
-h96
-tEGCS
-wh24
-t1.1
-wh24
-tor
-wh24
-tnewer.
-n40 0
-V2080
-H0
-to
-h96
-tPython
-wh72
-t1.5,
-wh72
-tCheck
-wh72
-tout
-wh72
-tftp://ftp.python.org
-wh72
-tor
-n40 0
-V2120
-H120
-tftp://ftp.cwi.nl/pub/python.
-n40 0
-V2240
-H0
-to
-h96
-tGUILE
-wh72
-t1.3,
-wh96
-tcheck
-wh72
-tout
-wh96
-thttp://www.gnu.org/soft
-Chy
-h24
-n40 0
-V2280
-H120
-tware/guile/guile.html.
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p3
-x font 1 R
-f1
-s10
-V160
-H696
-t-3-
-h672
-n40 0
-V280
-H0
-to
-h96
-tGNU
-wh24
-tmake.
-wh48
-tCheck
-wh24
-tout
-wh24
-tftp://ftp.gnu.org.
-n40 0
-V400
-H0
-to
-h96
-tFlex
-wh96
-t(version
-wh96
-t2.5.4
-wh72
-tor
-wh72
-tnewer).
-wh96
-tCheck
-wh72
-tout
-n40 0
-V440
-H120
-tftp://ftp.gnu.org.
-n40 0
-V560
-H0
-to
-h96
-tBison
-wh72
-t(version
-wh72
-t1.25
-wh72
-tor
-wh72
-tnewer).
-wh120
-tCheck
-wh96
-tout
-n40 0
-V600
-H120
-tftp://ftp.gnu.org.
-n40 0
-V720
-H0
-to
-h96
-tYodl.
-wh72
-tAll
-wh48
-tdocumentation
-wh48
-twill
-wh48
-tbe
-wh24
-tin
-wh24
-tYodl.
-wh24
-t(1.30.17)
-n40 0
-V760
-H120
-tftp://ftp.lilypond.org/pub/yodl
-n40 0
-V880
-H0
-to
-h96
-tThe
-wh24
-tgeometry
-wh24
-tpackage
-wh24
-tfor
-wh24
-tLaTeX
-wh24
-tis
-wh24
-tneeded
-wh24
-tto
-wh24
-tuse
-wh24
-tly2dvi.
-n40 0
-V920
-H120
-tAvailable
-wh264
-tat
-wh240
-tftp://ftp.ctan.org/tex-
-n40 0
-V960
-H120
-tarchive/macros/latex/contrib/supported/geometry
-wh48
-tor
-wh48
-tat
-n40 0
-V1000
-H120
-tmirror
-wh24
-tsite
-wh24
-tftp://ftp.dante.de
-n40 0
-x font 3 B
-f3
-V1120
-H0
-t4:
-wh24
-tRUNNING
-n40 0
-f1
-V1240
-H0
-tGNU
-wh48
-tLilyPond
-wh24
-tdoes
-wh24
-tuse
-wh24
-ta
-wh24
-tlot
-wh24
-tof
-wh24
-tresources.
-wh24
-tFor
-wh24
-toperation
-wh24
-tyou
-n40 0
-V1280
-H0
-tneed
-wh24
-tthe
-wh24
-tfollowing
-wh24
-tsoftware
-n40 0
-V1400
-H0
-to
-h96
-tTeX
-n40 0
-V1480
-H0
-to
-h96
-tA
-wh72
-tPostScript
-wh72
-tprinter
-wh72
-tand/or
-wh72
-tviewer
-wh72
-t(such
-wh72
-tas
-n40 0
-V1520
-H120
-tGhostscript)
-wh48
-tis
-wh48
-tstrongly
-wh24
-trecommended.
-wh48
-tXdvi
-wh24
-twill
-wh24
-tshow
-n40 0
-V1560
-H120
-tall
-wh24
-tembedded
-wh24
-tPostScript
-wh24
-ttoo
-wh48
-tif
-wh48
-tyou
-wh48
-thave
-wh48
-tGhostscript
-n40 0
-V1600
-H120
-tinstalled.
-n40 0
-V1680
-H0
-to
-h96
-tGUILE
-wh96
-t1.3,
-wh96
-tcheck
-wh96
-tout
-wh72
-thttp://www.gnu.org/pro
-Chy
-h24
-n40 0
-V1720
-H120
-tgrams/guile.html
-n40 0
-V1800
-H0
-tFor
-wh24
-trunning
-wh24
-tLilyPond
-wh24
-tsuccessfully
-wh24
-tyou
-wh24
-thave
-wh24
-tto
-wh24
-thelp
-wh48
-tTeX
-wh48
-tand
-n40 0
-V1840
-H0
-tMetaFont
-wh48
-tfind
-wh48
-tvarious
-wh24
-tfiles.
-wh48
-tThe
-wh24
-trecommended
-wh24
-tway
-wh24
-tof
-wh24
-tdoing
-n40 0
-V1880
-H0
-tso
-wh24
-tis
-wh24
-tadjusting
-wh24
-tthe
-wh24
-tenvironment
-wh24
-tvariables
-wh48
-tin
-wh48
-tthe
-wh48
-tstart-up
-n40 0
-V1920
-H0
-tscripts
-wh48
-tof
-wh48
-tyour
-wh48
-tshell.
-wh72
-tAn
-wh24
-texample
-wh24
-tis
-wh24
-tgiven
-wh24
-there
-wh24
-tfor
-wh24
-tthe
-n40 0
-V1960
-H0
-tBourne
-wh24
-tshell:
-n40 0
-V2160
-H120
-texport
-wh24
-tMFINPUTS="/usr/local/share/lilypond/mf:"
-n40 0
-V2200
-H120
-texport
-wh24
-tTEXINPUTS="/usr/local/share/lilypond/tex:/usr/local/share/lilypond/ps:"
-n40 0
-V2400
-H0
-tThe
-wh24
-tempty
-wh24
-tpath
-wh24
-tcomponent
-wh24
-trepresents
-wh48
-tand
-wh24
-tMetaFont
-Caa
-h24
-ts
-wh48
-tdefault
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p4
-x font 1 R
-f1
-s10
-V160
-H696
-t-4-
-h672
-n40 0
-V280
-H0
-tsearch
-wh48
-tpaths.
-wh48
-tScripts
-wh24
-twith
-wh24
-tthe
-wh24
-tproper
-wh24
-tpaths
-wh24
-tfor
-wh24
-tthe
-wh24
-tbourne
-n40 0
-V320
-H0
-tand
-wh72
-tC-shell
-wh72
-trespectively
-wh72
-tare
-wh72
-tgenerated
-wh72
-tin
-wx font 3 B
-f3
-h72
-tbuild
-Chy
-h24
-n40 0
-V360
-H0
-tscripts/out/lilypond-profile
-wf1
-h48
-tand
-wf3
-h24
-tbuildscripts/out/lilypond-
-n40 0
-V400
-H0
-tlogin
-wf1
-h24
-tduring
-wh24
-tcompilation.
-n40 0
-V480
-H0
-tLilyPond
-wh24
-tis
-wh24
-ta
-wh24
-thideously
-wh24
-tslow
-wh24
-tprogram.
-wh48
-tA
-wh24
-tfast
-wh24
-tCPU
-wh24
-tand
-wh24
-tplenty
-n40 0
-V520
-H0
-tof
-wh24
-tRAM
-wh24
-tis
-wh24
-trecommended
-wh24
-tfor
-wh24
-tcomfortable
-wh24
-tuse.
-n40 0
-f3
-V640
-H0
-t5:
-wh24
-tWEBSITE
-n40 0
-f1
-V760
-H0
-tIf
-wh48
-tyou
-wh48
-twant
-wh48
-tto
-wh48
-tauto-generate
-wh24
-tLily
-Caa
-h24
-ts
-wh24
-twebsite,
-wh24
-tyou
-Caa
-h24
-tll
-wh24
-tneed
-n40 0
-V800
-H0
-tsome
-wh24
-tadditional
-wh24
-tconversion
-wh24
-ttools.
-n40 0
-V920
-H0
-to
-h96
-txpmtoppm
-wh24
-t(from
-wh24
-tthe
-wh24
-tPortable
-wh24
-tBitmap
-wh24
-tUtilities)
-wh24
-t(For
-wh24
-tRed
-Chy
-h24
-n40 0
-V960
-H120
-tHat
-wh48
-tLinux
-wh48
-tusers:
-wh48
-tit
-wh48
-tis
-wh48
-tincluded
-wh24
-twithin
-wh24
-tthe
-wh24
-tpackage
-n40 0
-V1000
-H120
-tlibgr-progs).
-n40 0
-V1080
-H0
-to
-h96
-tBib2html
-wh24
-thttp://pertsserver.cs.uiuc.edu/~hull/bib2html.
-n40 0
-V1120
-H120
-tWhich,
-wh24
-tin
-wh24
-tturn
-wh24
-tdepends
-wh24
-ton
-wh24
-tman2html
-wh24
-tfor
-wh24
-tproper
-wh24
-tinstalla
-Chy
-h24
-n40 0
-V1160
-H120
-ttion.
-wh72
-tman2html
-wh48
-tcan
-wh48
-tbe
-wh72
-thad
-wh72
-tfrom
-wh72
-thttp://askdon
-Chy
-h24
-n40 0
-V1200
-H120
-tald.ask.uni-karlsruhe.de/hppd/hpux/Network
-Chy
-h24
-n40 0
-V1240
-H120
-ting/WWW/Man2html-1.05.
-n40 0
-V1320
-H120
-tTeTeX
-wh24
-tusers
-wh24
-tshould
-wh24
-tnot
-wh24
-tforget
-wh24
-tto
-wh24
-trerun
-wh24
-ttexhash.
-n40 0
-V1400
-H0
-tBuilding
-wh24
-tthe
-wh24
-twebsite
-wh24
-trequires
-wh24
-tpnmtopng.
-wh48
-tThe
-wh24
-tversion
-wh24
-tof
-wf3
-h24
-tpnm
-Chy
-h24
-n40 0
-V1440
-H0
-ttopng
-wf1
-h24
-tthat
-wh24
-tis
-wh24
-tdistributed
-wh24
-twith
-wh24
-tRedHat
-wh24
-t5.1
-wh24
-tand
-wh24
-t5.2
-wh24
-tcontains
-wh24
-ta
-n40 0
-V1480
-H0
-tbug:
-wh24
-tpnmtopng
-wh24
-tis
-wh24
-tdynamically
-wh24
-tlinked
-wh24
-tto
-wh24
-tthe
-wh24
-twrong
-wh24
-tversion
-wh48
-tof
-n40 0
-V1520
-H0
-tlibpng.
-wh72
-tRecompile
-wh48
-tit
-wh48
-tfrom
-wh24
-tsource,
-wh24
-tand
-wh24
-tmake
-wh24
-tsure
-wh24
-tthat
-wh24
-tthe
-n40 0
-V1560
-H0
-tpnmtopng
-wh24
-tbinary
-wh24
-tis
-wh24
-tlinked
-wh24
-tstatically
-wh24
-tto
-wh24
-tthe
-wh24
-tlibpng
-wh48
-tthat
-wh48
-tis
-n40 0
-V1600
-H0
-tincluded
-wh48
-tin
-wh24
-tlibgr.
-wh72
-tRedHat
-wh24
-t6.0
-wh24
-tdoes
-wh24
-tnot
-wh24
-thave
-wh24
-tthis
-wh24
-tproblem.
-n40 0
-V1840
-H144
-ttar
-wh24
-txzf
-wh24
-tlibgr-2.0.13.tar.gz
-n40 0
-V1880
-H264
-tmake
-n40 0
-V1920
-H264
-tcd
-wh24
-tpng
-n40 0
-V1960
-H264
-trm
-wh24
-tlibpng.so*
-n40 0
-V2000
-H264
-tmake
-wh24
-tpnmtopng
-n40 0
-V2240
-H0
-tYou
-wh24
-tcan
-wh24
-tthen
-wh24
-tinstall
-wh24
-tthe
-wh24
-tnew
-wh24
-tpnmtopng
-wh24
-tinto
-wh24
-t/usr/local/bin/
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p5
-x font 1 R
-f1
-s10
-V160
-H696
-t-5-
-h672
-n40 0
-x font 3 B
-f3
-V280
-H0
-t6:
-wh24
-tCONFIGURING
-wh24
-tand
-wh24
-tCOMPILING
-n40 0
-f1
-V400
-H0
-tto
-wh24
-tinstall
-wh24
-tGNU
-wh24
-tLilyPond,
-wh24
-tsimply
-wh24
-ttype:
-n40 0
-V640
-H240
-tgunzip
-wh24
-t-c
-wh24
-tlilypond-x.y.z
-wh24
-t|
-wh24
-ttar
-wh24
-txf
-wh24
-t-
-n40 0
-V680
-H240
-tcd
-wh24
-tlilypond-x.y.z
-n40 0
-V720
-H240
-t./configure
-h216
-t#
-wh24
-tfill
-wh24
-tin
-wh24
-tyour
-wh24
-tstandard
-wh24
-tprefix
-wh24
-twith
-wh24
-t--prefix
-n40 0
-V760
-H240
-tmake
-n40 0
-V800
-H240
-tmake
-wh24
-tinstall
-n40 0
-V1040
-H0
-tThis
-wh24
-twill
-wh24
-tinstall
-wh24
-ta
-wh24
-tnumber
-wh24
-tof
-wh24
-tfiles,
-wh24
-tsomething
-wh24
-tclose
-wh24
-tto:
-n40 0
-V1280
-H240
-t/usr/local/man/man1/mi2mu.1
-n40 0
-V1320
-H240
-t/usr/local/man/man1/convert-mudela.1
-n40 0
-V1360
-H240
-t/usr/local/man/man1/mudela-book.1
-n40 0
-V1400
-H240
-t/usr/local/man/man1/lilypond.1
-n40 0
-V1440
-H240
-t/usr/local/bin/lilypond
-n40 0
-V1480
-H240
-t/usr/local/bin/mi2mu
-n40 0
-V1520
-H240
-t/usr/local/share/lilypond/*
-n40 0
-V1560
-H240
-t/usr/local/share/locale/{it,nl}/LC_MESSAGES/lilypond.mo
-n40 0
-V1800
-H0
-tThe
-wh24
-tabove
-wh24
-tassumes
-wh24
-tthat
-wh24
-tyou
-wh24
-tare
-wh24
-troot
-wh24
-tand
-wh24
-thave
-wh24
-tthe
-wh24
-tGNU
-wh48
-tdevel
-Chy
-h24
-n40 0
-V1840
-H0
-topment
-wh24
-ttools,
-wh24
-tand
-wh24
-tyour
-wh24
-tmake
-wh24
-tis
-wh24
-tGNU
-wh24
-tmake.
-wh48
-tIf
-wh24
-tthis
-wh24
-tis
-wh24
-tnot
-wh24
-tthe
-n40 0
-V1880
-H0
-tcase,
-wh24
-tyou
-wh24
-tcan
-wh24
-tadjust
-wh48
-tyour
-wh48
-tenvironment
-wh48
-tvariables
-wh48
-tto
-wh48
-tyour
-n40 0
-V1920
-H0
-ttaste:
-n40 0
-V2200
-H240
-texport
-wh24
-tCPPFLAGS="-I
-wh24
-t/home/me/my_include
-wh24
-t-DWEIRD_FOOBAR"
-n40 0
-V2240
-H240
-t./configure
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p6
-x font 1 R
-f1
-s10
-V160
-H696
-t-6-
-h672
-n40 0
-V280
-H0
-tCPPFLAGS
-wh24
-tare
-wh24
-tthe
-wh24
-tpreprocessor
-wh24
-tflags.
-n40 0
-V360
-H0
-tThe
-wh24
-tconfigure
-wh24
-tscript
-wh24
-tis
-wh24
-tCygnus
-wh24
-tconfigure,
-wh24
-tand
-wh24
-tit
-wh24
-twill
-wh24
-taccept
-n40 0
-x font 3 B
-f3
-V400
-H0
-t--help
-f1
-t.
-wh24
-tIf
-wh24
-tyou
-wh24
-tare
-wh24
-tnot
-wh24
-troot,
-wh24
-tyou
-wh24
-twill
-wh24
-tprobably
-wh24
-thave
-wh24
-tto
-wh48
-tmake
-n40 0
-V440
-H0
-tit
-wh24
-twith
-wh24
-ta
-wh24
-tdifferent
-wf3
-h24
-t--prefix
-wf1
-h24
-toption.
-wh48
-tOur
-wh24
-tfavourite
-wh24
-tlocation
-n40 0
-V480
-H0
-tis
-n40 0
-V760
-H240
-t./configure
-wh24
-t--prefix=$HOME/usr
-n40 0
-V1000
-H0
-tIn
-wh24
-tthis
-wh24
-tcase,
-wh24
-tyou
-wh24
-twill
-wh24
-thave
-wh24
-tto
-wh24
-tset
-wh24
-tup
-wh24
-tMFINPUTS,
-wh48
-tand
-wh48
-tTEXIN
-Chy
-h24
-n40 0
-V1040
-H0
-tPUTS
-wh24
-taccordingly.
-n40 0
-V1120
-H0
-tSince
-wh48
-tGNU
-wh48
-tLilyPond
-wh48
-tcurrently
-wh48
-tis
-wh24
-tbeta,
-wh24
-tyou
-wh24
-tare
-wh24
-tadvised
-wh24
-tto
-n40 0
-V1160
-H0
-talso
-wh24
-tuse
-n40 0
-V1440
-H240
-t--enable-debugging
-n40 0
-V1480
-H240
-t--enable-checking
-n40 0
-V1720
-H0
-tOptions
-wh24
-tto
-wh24
-tconfigure
-wh24
-tinclude:
-n40 0
-f3
-V1840
-H0
-t--enable-printing
-n40 0
-f1
-V1880
-H120
-tEnable
-wh24
-tdebugging
-wh24
-tprint
-wh24
-troutines
-wh24
-t(lilypond
-wf3
-h24
-t-D
-wf1
-h24
-toption)
-n40 0
-f3
-V1960
-H0
-t--enable-optimise
-n40 0
-f1
-V2000
-H120
-tSet
-wh24
-tmaximum
-wh24
-toptimisation:
-wh24
-tcompile
-wh24
-twith
-wf3
-h24
-t-O2
-f1
-t.
-wh72
-tThis
-wh48
-tcan
-n40 0
-V2040
-H120
-tbe
-wh48
-tunreliable
-wh48
-ton
-wh48
-tsome
-wh24
-tcompiler/platform
-wh24
-tcombinations
-n40 0
-V2080
-H120
-t(eg,
-wh24
-tDEC
-wh24
-tAlpha
-wh24
-tand
-wh24
-tPPC)
-n40 0
-f3
-V2160
-H0
-t--enable-profiling
-n40 0
-f1
-V2200
-H120
-tCompile
-wh24
-twith
-wh24
-tsupport
-wh24
-tfor
-wh24
-tprofiling.
-n40 0
-f3
-V2280
-H0
-t--enable-config
-n40 0
-f1
-V2320
-H120
-tOutput
-wh24
-tto
-wh24
-ta
-wh24
-tdifferent
-wh24
-tconfiguration
-wh24
-tfile.
-wh72
-tNeeded
-wh48
-tfor
-n40 0
-V2360
-H120
-tmulti-platform
-wh24
-tbuilds
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p7
-x font 1 R
-f1
-s10
-V160
-H696
-t-7-
-h672
-n40 0
-V280
-H0
-tAll
-wh48
-toptions
-wh24
-tare
-wh24
-tdocumented
-wh24
-tin
-wh24
-tthe
-wx font 3 B
-f3
-h24
-tconfigure
-wf1
-h24
-thelp
-wh24
-tThe
-wh24
-toption
-n40 0
-f3
-V320
-H0
-t--enable-optimise
-wf1
-h24
-tis
-wh24
-trecommended
-wh24
-tfor
-wh24
-tReal
-wh24
-tLife
-wh24
-tusage.
-n40 0
-V400
-H0
-tIf
-wh24
-tyou
-wh24
-tdo
-n40 0
-V680
-H240
-tmake
-wh24
-tall
-n40 0
-V920
-H0
-teverything
-wh24
-twill
-wh24
-tbe
-wh24
-tcompiled,
-wh24
-tbut
-wh24
-tnothing
-wh24
-twill
-wh24
-tbe
-wh48
-tinstalled.
-n40 0
-V960
-H0
-tThe
-wh48
-tresulting
-wh48
-tbinaries
-wh48
-tcan
-wh24
-tbe
-wh24
-tfound
-wh24
-tin
-wh24
-tthe
-wh24
-tsubdirectories
-n40 0
-f3
-V1000
-H0
-tout/
-wf1
-h24
-t(which
-wh24
-tcontain
-wh24
-tall
-wh24
-tfiles
-wh24
-tgenerated
-wh24
-tduring
-wh24
-tcompilation).
-n40 0
-f3
-V1120
-H0
-t7:
-wh24
-tCONFIGURING
-wh24
-tFOR
-wh24
-tMULTIPLE
-wh24
-tPLATFORMS
-n40 0
-f1
-V1240
-H0
-tIf
-wh24
-tyou
-wh24
-twant
-wh24
-tto
-wh24
-tcompile
-wh24
-tLilyPond
-wh24
-twith
-wh24
-tdifferent
-wh24
-tconfiguration
-n40 0
-V1280
-H0
-tsettings,
-wh24
-tthen,
-wh24
-tyou
-wh48
-tcan
-wh48
-tuse
-wh48
-tthe
-wf3
-h48
-t--enable-config
-wf1
-h48
-toption.
-n40 0
-V1320
-H0
-tExample:
-wh48
-tsuppose
-wh24
-tI
-wh24
-twant
-wh24
-tto
-wh24
-tbuild
-wh24
-twith
-wh24
-tand
-wh72
-twithout
-wh24
-tprofil
-Chy
-h24
-n40 0
-V1360
-H0
-ting.
-wh48
-tThen
-wh24
-tI
-Caa
-h24
-td
-wh24
-tuse
-wh24
-tthe
-wh24
-tfollowing
-wh24
-tfor
-wh24
-tthe
-wh24
-tnormal
-wh24
-tbuild,
-n40 0
-V1640
-H264
-t./configure
-wh24
-t--prefix=~
-wh24
-t--disable-optimise
-wh24
-t--enable-checking
-n40 0
-V1680
-H264
-tmake
-n40 0
-V1720
-H264
-tmake
-wh24
-tinstall
-n40 0
-V1960
-H0
-tand
-wh24
-tfor
-wh24
-tthe
-wh24
-tprofiling
-wh24
-tversion,
-wh24
-tI
-wh24
-tspecify
-wh24
-ta
-wh24
-tdifferent
-wh24
-tconfig
-Chy
-h24
-n40 0
-V2000
-H0
-turation.
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p8
-x font 1 R
-f1
-s10
-V160
-H696
-t-8-
-h672
-n40 0
-V280
-H264
-t./configure
-wh24
-t--prefix=~
-wh24
-t--enable-profiling
-wh24
-t--enable-config=optprof
-wh24
-t--enable-optimise
-wh24
-t--disable-checking
-n40 0
-V320
-H264
-tmake
-wh24
-tconfig=optprof
-n40 0
-V360
-H264
-tmake
-wh24
-tconfig=optprof
-wh24
-tinstall
-n40 0
-x font 3 B
-f3
-V640
-H0
-t8:
-wh24
-tINSTALLING
-n40 0
-f1
-V760
-H0
-tIf
-wh24
-tyou
-wh24
-thave
-wh24
-tdone
-wh24
-ta
-wh24
-tsuccessful
-wh24
-tmake,
-wh24
-tthen
-wh24
-ta
-wh24
-tsimple
-n40 0
-V1040
-H240
-tmake
-wh24
-tinstall
-n40 0
-V1280
-H0
-tshould
-wh24
-tdo
-wh24
-tthe
-wh24
-ttrick.
-n40 0
-V1360
-H0
-tIf
-wh24
-tyou
-wh24
-tare
-wh24
-tdoing
-wh24
-tan
-wh24
-tupgrade,
-wh24
-tplease
-wh24
-tremember
-wh24
-tto
-wh24
-tremove
-wh24
-tobso
-Chy
-h24
-n40 0
-V1400
-H0
-tlete
-wf3
-h24
-t.pk
-wf1
-h24
-tand
-wf3
-h24
-t.tfm
-wf1
-h24
-tfiles
-wh24
-tof
-wh24
-tthe
-wh24
-tfonts.
-wh72
-tA
-wh48
-tscript
-wh48
-thas
-wh48
-tbeen
-n40 0
-V1440
-H0
-tprovided
-wh24
-tto
-wh24
-tdo
-wh24
-tthe
-wh24
-twork
-wh24
-tfor
-wh24
-tyou,
-wh24
-tsee
-wf3
-h24
-tbin/clean-fonts.sh
-f1
-t.
-n40 0
-f3
-V1560
-H0
-tCAVEATS
-n40 0
-f1
-V1720
-H0
-to
-h96
-tThe
-wh48
-t-O2
-wh48
-toption
-wh72
-ttriggers
-wh72
-tbugs
-wh24
-ton
-wh24
-tvarious
-wh24
-tplatforms
-n40 0
-V1760
-H120
-t(PowerPC,
-wh24
-tAlpha).
-wh72
-tIf
-wh48
-tyou
-wh48
-texperience
-wh48
-tproblems,
-wh48
-tyou
-n40 0
-V1800
-H120
-tshould
-wh24
-tfirst
-wh24
-ttry
-wh48
-tturning
-wh24
-toff
-wh24
-tthis.
-n40 0
-f3
-V1920
-H0
-tEXAMPLE
-n40 0
-f1
-V2040
-H0
-tThis
-wh24
-tis
-wh24
-twhat
-wh24
-tI
-wh24
-ttype
-wh24
-tin
-wh24
-tmy
-wh24
-txterm:
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p9
-x font 1 R
-f1
-s10
-V160
-H696
-t-9-
-h672
-n40 0
-V280
-H240
-tlilypond
-wh24
-tsomeinput.ly
-n40 0
-V320
-H240
-ttex
-wh24
-tsomeinput.tex
-n40 0
-V360
-H240
-txdvi
-wh24
-tsomeinput&
-n40 0
-V600
-H0
-tThis
-wh24
-tis
-wh24
-twhat
-wh24
-tthe
-wh24
-toutput
-wh24
-tlooks
-wh24
-tlike
-wh24
-tover
-wh24
-there:
-n40 0
-V880
-H240
-tGNU
-wh24
-tLilyPond
-wh24
-t0.0.78
-wh24
-t#4/FlowerLib
-wh24
-t1.1.24
-wh24
-t#0
-n40 0
-V920
-H240
-tParsing
-wh24
-t...
-wh24
-t[/home/hw/share/lilypond/init//
-n40 0
-V960
-H360
-t<..etc..>
-n40 0
-V1000
-H360
-tinit//performer.ly]]][input/kortjakje.ly]
-n40 0
-V1040
-H240
-tCreating
-wh24
-telements
-wh24
-t...[8][16][24][25]
-n40 0
-V1080
-H240
-tPreprocessing
-wh24
-telements...
-n40 0
-V1120
-H240
-tCalculating
-wh24
-tcolumn
-wh24
-tpositions
-wh24
-t...
-wh24
-t[14][25]
-n40 0
-V1160
-H240
-tPostprocessing
-wh24
-telements...
-n40 0
-V1200
-H240
-tTeX
-wh24
-toutput
-wh24
-tto
-wh24
-tsomeinput.tex
-wh24
-t...
-n40 0
-V1240
-H240
-tCreating
-wh24
-tMIDI
-wh24
-telements
-wh24
-t...MIDI
-wh24
-toutput
-wh24
-tto
-wh24
-tsomeinput.midi
-wh24
-t...
-n40 0
-V1360
-H240
-thw:~/musix/spacer$
-wh24
-txdvi
-wh24
-tsomeinput&
-n40 0
-V1400
-H240
-t[1]
-wh24
-t855
-n40 0
-V1640
-H0
-tCheck
-wh24
-tout
-wh24
-tthe
-wh24
-tinput
-wh24
-tfiles,
-wh24
-tsome
-wh24
-tof
-wh24
-tthem
-wh24
-thave
-wh24
-tcomments
-wh24
-tPlease
-n40 0
-V1680
-H0
-trefer
-wh24
-tto
-wh24
-tthe
-wh24
-tman
-wh24
-tpage
-wh24
-tfor
-wh24
-tmore
-wh24
-tinformation.
-n40 0
-x font 3 B
-f3
-V1800
-H0
-t9:
-wh24
-tREDHAT
-wh24
-tLINUX
-n40 0
-f1
-V1920
-H0
-tRedHat
-wh24
-tLinux
-wh24
-tusers
-wh24
-tcan
-wh24
-tcompile
-wh24
-tan
-wh24
-tRPM.
-wh24
-tA
-wh48
-tspec
-wh48
-tfile
-wh48
-tis
-wh48
-tin
-n40 0
-f3
-V1960
-H0
-tmake/out/lilypond.spec
-f1
-t,
-wh48
-tit
-wh48
-tis
-wh48
-tdistributed
-wh48
-talong
-wh24
-twith
-wh24
-tthe
-n40 0
-V2000
-H0
-tsources.
-n40 0
-V2080
-H0
-tYou
-wh24
-tcan
-wh24
-tmake
-wh24
-tthe
-wh24
-trpm
-wh24
-tby
-wh24
-tissuing
-n40 0
-V2560
-H1440
-n40 0
-V2640
-p10
-x font 1 R
-f1
-s10
-V160
-H672
-t-10-
-h672
-n40 0
-V280
-H240
-trpm
-wh24
-t-tb
-wh24
-tlilypond-x.y.z.tar.gz
-n40 0
-V320
-H240
-trpm
-wh24
-t-i
-wh24
-t/usr/src/redhat/RPMS/i386/lilypond-x.y.z
-n40 0
-V560
-H0
-tPrecompiled
-wh72
-ti386
-wh72
-teRedHat
-wh72
-tRPMS
-wh72
-tare
-wh72
-tavailable
-wh72
-tfrom
-n40 0
-V600
-H0
-thttp://linux.umbc.edu/software/lilypond/rpms/.
-n40 0
-x font 3 B
-f3
-V720
-H0
-t10:
-wh24
-tDEBIAN
-wh24
-tGNU/LINUX
-n40 0
-f1
-V840
-H0
-tA
-wh48
-tDebian
-wh48
-tpackage
-wh48
-tis
-wh48
-talso
-wh48
-tavailable;
-wh24
-tcontact
-wh24
-tAnthony
-wh24
-tFok
-n40 0
-V880
-H0
-tfoka@debian.org
-wh24
-t<foka@debian.org>.
-wh48
-tThe
-wh24
-tbuild
-wh24
-tscripts
-wh24
-tare
-wh24
-tin
-n40 0
-V920
-H0
-tthe
-wh24
-tsubdirectory
-wf3
-h24
-tdebian/
-f1
-t.
-n40 0
-f3
-V1040
-H0
-t11:
-wh24
-tWINDOWS
-wh24
-tNT/95
-n40 0
-f1
-V1160
-H0
-tSeparate
-wh24
-tinstructions
-wh24
-ton
-wh24
-tbuilding
-wh24
-tfor
-wh24
-tW32
-wh24
-tare
-wh24
-tavaible
-wh24
-tin
-wh24
-tthe
-n40 0
-V1200
-H0
-tfile
-wh24
-tREADME-W32.yo.
-n40 0
-f3
-V1320
-H0
-t12:
-wh24
-tAUTHORS
-n40 0
-f1
-V1440
-H0
-tHan-Wen
-wh24
-tNienhuys
-wh24
-t<hanwen@cs.uu.nl>
-n40 0
-V1520
-H0
-tJan
-wh24
-tNieuwenhuizen
-wh24
-t<janneke@gnu.org>
-n40 0
-V1600
-H0
-tHave
-wh24
-tfun!
-n40 0
-V2560
-H1440
-n40 0
-x trailer
-V2640
-x stop
+INSTALL - compiling and installing GNU LilyPond
+***********************************************
+
+
+1 Compilation
+ 1.1 Overview of compiling
+ 1.2 Requirements
+ 1.2.1 Requirements for running LilyPond
+ 1.2.2 Requirements for compiling LilyPond
+ Fedora
+ Linux Mint
+ OpenSUSE
+ Ubuntu
+ Other
+ 1.2.3 Requirements for building documentation
+ 1.3 Getting the source code
+ 1.4 Configuring ‘make’
+ 1.4.1 Running ‘./autogen.sh’
+ 1.4.2 Running ‘../configure’
+ Configuration options
+ Checking build dependencies
+ Configuring target directories
+ 1.5 Compiling LilyPond
+ 1.5.1 Using ‘make’
+ 1.5.2 Saving time with the ‘-j’ option
+ 1.5.3 Compiling for multiple platforms
+ 1.5.4 Useful ‘make’ variables
+ 1.6 Post-compilation options
+ 1.6.1 Installing LilyPond from a local build
+ 1.6.2 Generating documentation
+ Documentation editor’s edit/compile cycle
+ Building documentation
+ Building a single document
+ Saving time with ‘CPU_COUNT’
+ AJAX search
+ Installing documentation
+ Building documentation without compiling
+ 1.6.3 Testing LilyPond binary
+ 1.7 Problems
+ Compiling on MacOS X
+ Solaris
+ FreeBSD
+ International fonts
+ Using lilypond python libraries
+ 1.8 Concurrent stable and development versions
+ 1.9 Build system
+1 Compilation
+*************
+
+1.1 Overview of compiling
+=========================
+
+Compiling LilyPond from source is an involved process, and is only
+recommended for developers and packagers. Typical program users are
+instead encouraged to obtain the program from a package manager (on
+Unix) or by downloading a precompiled binary configured for a specific
+operating system. Pre-compiled binaries are available on the *note
+(lilypond-web)Download:: page.
+
+ Compiling LilyPond from source is necessary if you want to build,
+install, or test your own version of the program.
+
+ A successful compile can also be used to generate and install the
+documentation, incorporating any changes you may have made. However, a
+successful compile is not a requirement for generating the
+documentation. The documentation can be built using a Git repository in
+conjunction with a locally installed copy of the program. For more
+information, see *note Building documentation without compiling::.
+
+ Attempts to compile LilyPond natively on Windows have been
+unsuccessful, though a workaround is available (see *note
+(lilypond-contributor)LilyDev::).
+
+1.2 Requirements
+================
+
+1.2.1 Requirements for running LilyPond
+---------------------------------------
+
+This section contains the list of separate software packages that are
+required to run LilyPond.
+
+ • DejaVu fonts (http://www.dejavu-fonts.org/) These are normally
+ installed by default.
+
+ • FontConfig (http://www.fontconfig.org/) Use version 2.4.0 or newer.
+
+ • Freetype (http://www.freetype.org/) Use version 2.1.10 or newer.
+
+ • Ghostscript (http://www.ghostscript.com) Use version 8.60 or newer.
+
+ • Guile (http://www.gnu.org/software/guile/guile.html) Use version
+ 1.8.8. Version 2.x of Guile is not currently supported.
+
+ • Pango (http://www.pango.org/) User version 1.12 or newer.
+
+ • Python (http://www.python.org) Use version 2.4 or newer.
+
+ • International fonts. For example:
+
+ Fedora:
+
+ fonts-arabic
+ fonts-hebrew
+ fonts-ja
+ fonts-xorg-truetype
+ taipeifonts
+ ttfonts-ja
+ ttfonts-zh_CN
+
+ Debian based distributions:
+
+ emacs-intl-fonts
+ fonts-ipafont-gothic
+ fonts-ipafont-mincho
+ xfonts-bolkhov-75dpi
+ xfonts-cronyx-75dpi
+ xfonts-cronyx-100dpi
+ xfonts-intl-.*
+
+ These are normally installed by default and are required only to
+ create music with international text or lyrics.
+
+1.2.2 Requirements for compiling LilyPond
+-----------------------------------------
+
+This section contains instructions on how to quickly and easily get all
+the software packages required to build LilyPond.
+
+ Most of the more popular Linux distributions only require a few
+simple commands to download all the software needed. For others, there
+is an explicit list of all the individual packages (as well as where to
+get them from) for those that are not already included in your
+distributions’ own repositories.
+
+Fedora
+......
+
+The following instructions were tested on ‘Fedora’ versions 22 & 23 and
+will download all the software required to both compile LilyPond and
+build the documentation.
+
+ • Download and install all the LilyPond build-dependencies
+ (approximately 700MB);
+
+ sudo dnf builddep lilypond --nogpgcheck
+
+ • Download and install additional ‘build’ tools required for
+ compiling;
+
+ sudo dnf install autoconf gcc-c++
+
+ • Download ‘texi2html 1.82’ directly from:
+ <http://download.savannah.gnu.org/releases/texi2html/texi2html-1.82.tar.gz>;
+
+ ‘texi2html’ is only required if you intend to compile LilyPond’s
+ own documentation (e.g. to help with any document writing). The
+ version available in the Fedora repositories is too new and will
+ not work. Extract the files into an appropriate location and then
+ run the commands;
+
+ ./configure
+ make
+ sudo make install
+
+ This should install ‘texi2html 1.82’ into ‘/usr/local/bin’, which
+ will normally take priority over ‘/usr/bin’ where the later,
+ pre-installed versions gets put. Now verify that your operating
+ system is able to see the correct version of ‘texi2html’.
+
+ texi2html --version
+
+ • Although not ‘required’ to compile LilyPond, if you intend to
+ contribute to LilyPond (codebase or help improve the documentation)
+ then it is recommended that you also need to install ‘git’.
+
+ sudo dnf install git
+
+ Also see *note (lilypond-contributor)Starting with Git::.
+
+ • To use the ‘lily-git.tcl’ GUI;
+
+ sudo dnf install tk
+
+ See *note (lilypond-contributor)lily-git::.
+
+ Note: By default, when building LilyPond’s documentation,
+ ‘pdfTeX’ is be used. However ligatures (fi, fl, ff etc.) may
+ not be printed in the PDF output. In this case XeTeX can be
+ used instead. Download and install the ‘texlive-xetex’
+ package.
+
+ sudo dnf install texlive-xetex
+
+ The scripts used to build the LilyPond documentation will use
+ ‘XeTex’ instead of ‘pdfTex’ to generate the PDF documents if
+ it is available. No additional configuration is required.
+
+Linux Mint
+..........
+
+The following instructions were tested on ‘Linux Mint 17.1’ and ‘LMDE -
+Betsy’ and will download all the software required to both compile
+LilyPond and build the documentation..
+
+ • Enable the _sources_ repository;
+
+ 1. Using the _Software Sources_ GUI (located under
+ _Administration_).
+
+ 2. Select _Official Repositories_.
+
+ 3. Check the _Enable source code repositories_ box under the
+ _Source Code_ section.
+
+ 4. Click the _Update the cache_ button and when it has completed,
+ close the _Software Sources_ GUI.
+
+ • Download and install all the LilyPond build-dependencies
+ (approximately 200MB);
+
+ sudo apt-get build-dep lilypond
+
+ • Download and install additional ‘build’ tools required for
+ compiling;
+
+ sudo apt-get install autoconf fonts-texgyre texlive-lang-cyrillic
+
+ • Although not ‘required’ to compile LilyPond, if you intend to
+ contribute to LilyPond (codebase or help improve the documentation)
+ then it is recommended that you also need to install ‘git’.
+
+ sudo apt-get install git
+
+ Also see *note (lilypond-contributor)Starting with Git::.
+
+ • To use the ‘lily-git.tcl’ GUI;
+
+ sudo apt-get install tk
+
+ Also see *note (lilypond-contributor)lily-git::.
+
+ Note: By default, when building LilyPond’s documentation,
+ ‘pdfTeX’ is be used. However ligatures (fi, fl, ff etc.) may
+ not be printed in the PDF output. In this case XeTeX can be
+ used instead. Download and install the ‘texlive-xetex’
+ package.
+
+ sudo apt-get install texlive-xetex
+
+ The scripts used to build the LilyPond documentation will use
+ ‘XeTex’ instead of ‘pdfTex’ to generate the PDF documents if
+ it is available. No additional configuration is required.
+
+OpenSUSE
+........
+
+The following instructions were tested on ‘OpenSUSE 13.2’ and will
+download all the software required to both compile LilyPond and build
+the documentation.
+
+ • Add the _sources_ repository;
+
+ sudo zypper addrepo -f \
+ "http://download.opensuse.org/source/distribution/13.2/repo/oss/" sources
+
+ • Download and install all the LilyPond build-dependencies
+ (approximately 680MB);
+
+ sudo zypper source-install lilypond
+
+ • Download and install additional ‘build’ tools required for
+ compiling;
+
+ sudo zypper install make
+
+ • Although not ‘required’ to compile LilyPond, if you intend to
+ contribute to LilyPond (codebase or help improve the documentation)
+ then it is recommended that you also need to install ‘git’.
+
+ sudo zypper install git
+
+ Also see *note (lilypond-contributor)Starting with Git::.
+
+ • To use the ‘lily-git.tcl’ GUI;
+
+ sudo zypper install tk
+
+ Also see *note (lilypond-contributor)lily-git::.
+
+ Note: By default, when building LilyPond’s documentation,
+ ‘pdfTeX’ is be used. However ligatures (fi, fl, ff etc.) may
+ not be printed in the PDF output. In this case XeTeX can be
+ used instead. Download and install the ‘texlive-xetex’
+ package.
+
+ sudo zypper install texlive-xetex
+
+ The scripts used to build the LilyPond documentation will use
+ ‘XeTex’ instead of ‘pdfTex’ to generate the PDF documents if
+ it is available. No additional configuration is required.
+
+Ubuntu
+......
+
+The following commands were tested on Ubuntu versions ‘14.04 LTS’,
+‘14.10’ and ‘15.04’ and will download all the software required to both
+compile LilyPond and build the documentation.
+
+ • Download and install all the LilyPond build-dependencies
+ (approximately 200MB);
+
+ sudo apt-get build-dep lilypond
+
+ • Download and install additional ‘build’ tools required for
+ compiling;
+
+ sudo apt-get install autoconf fonts-texgyre texlive-lang-cyrillic
+
+ • Although not ‘required’ to compile LilyPond, if you intend to
+ contribute to LilyPond (codebase or help improve the documentation)
+ then it is recommended that you also need to install ‘git’.
+
+ sudo apt-get install git
+
+ Also see *note (lilypond-contributor)Starting with Git::.
+
+ • To use the ‘lily-git.tcl’ GUI;
+
+ sudo apt-get install tk
+
+ Also see *note (lilypond-contributor)lily-git::.
+
+ Note: By default, when building LilyPond’s documentation,
+ ‘pdfTeX’ is be used. However ligatures (fi, fl, ff etc.) may
+ not be printed in the PDF output. In this case XeTeX can be
+ used instead. Download and install the ‘texlive-xetex’
+ package.
+
+ sudo apt-get install texlive-xetex
+
+ The scripts used to build the LilyPond documentation will use
+ ‘XeTex’ instead of ‘pdfTex’ to generate the PDF documents if
+ it is available. No additional configuration is required.
+
+Other
+.....
+
+The following individual software packages are required just to compile
+LilyPond.
+
+ • GNU Autoconf (http://www.gnu.org/software/autoconf)
+
+ • GNU Bison (http://www.gnu.org/software/bison/)
+
+ Use version ‘2.0’ or newer.
+
+ • GNU Compiler Collection (http://gcc.gnu.org/)
+
+ Use version ‘3.4’ or newer (‘4.x’ recommended).
+
+ • Flex (http://flex.sourceforge.net/)
+
+ • FontForge (http://fontforge.sf.net/)
+
+ Use version ‘20060125’ or newer (we recommend using at least
+ ‘20100501’); it must also be compiled with the ‘--enable-double’
+ switch, else this can lead to inaccurate intersection calculations
+ which end up with poorly-rendered glyphs in the output.
+
+ • GNU gettext (http://www.gnu.org/software/gettext/gettext.html)
+
+ Use version ‘0.17’ or newer.
+
+ • GNU Make (http://www.gnu.org/software/make/)
+
+ Use version ‘3.78’ or newer.
+
+ • MetaFont (http://metafont.tutorial.free.fr/)
+
+ The ‘mf-nowin’, ‘mf’, ‘mfw’ or ‘mfont’ binaries are usually
+ packaged along with TeX (http://www.latex-project.org/ftp.html).
+
+ • MetaPost (http://cm.bell-labs.com/who/hobby/MetaPost.html)
+
+ The ‘mpost’ binary is also usually packaged with TeX
+ (http://www.latex-project.org/ftp.html).
+
+ • Perl (http://www.perl.org/)
+
+ • Texinfo (http://www.gnu.org/software/texinfo/)
+
+ Use version ‘4.11’ or newer.
+
+ • Type 1 utilities (http://www.lcdf.org/~eddietwo/type/#t1utils)
+
+ Use version ‘1.33’ or newer.
+
+ • Cyrillic fonts (https://www.ctan.org/pkg/cyrillic?lang=en)
+
+ Often packaged in repositories as ‘texlive-lang-cyrillic’.
+
+ • TeX Gyre ‘OTF’ font packages. As of LilyPond version ‘2.19.26’,
+ the previous default serif, san serif and monospace fonts now use
+ Tex Gyre’s _Schola_, _Heros_ and _Cursor_ fonts respectively. Also
+ See *note (lilypond-notation)Fonts::.
+
+ Some distributions do not always provide ‘OTF’ font files in the
+ Tex Gyre packages from their repositories. Use the command
+ ‘fc-list | grep texgyre’ to list the fonts available to your system
+ and check that the appropriate ‘*.otf’ files are reported. If they
+ are not then download and manually extract the ‘OTF’ files to
+ either your local ‘~/.fonts/’ directory or use the ‘configure’
+ command and the ‘--with-texgyre-dir=/path_to_otf_files/’ option.
+
+ The following font families are required:
+
+ Schola (http://www.gust.org.pl/projects/e-foundry/tex-gyre/schola),
+ Heros (http://www.gust.org.pl/projects/e-foundry/tex-gyre/heros)
+ and Cursor
+ (http://www.gust.org.pl/projects/e-foundry/tex-gyre/cursor).
+
+1.2.3 Requirements for building documentation
+---------------------------------------------
+
+The entire set of documentation for the most current build of LilyPond
+is available online at
+<http://lilypond.org/doc/v2.19/Documentation/web/development>, but you
+can also build them locally from the source code. This process requires
+some additional tools and packages.
+
+ Note: If the instructions for one of the previously listed
+ Linux in the previous section (*note
+ (lilypond-contributor)Requirements for compiling LilyPond::)
+ have been used, then the following can be ignored as the
+ software should already be installed.
+
+ • Everything listed in *note Requirements for compiling LilyPond::
+
+ • ImageMagick (http://www.imagemagick.org/)
+
+ • Netpbm (http://netpbm.sourceforge.net/)
+
+ • gzip (http://gzip.org/)
+
+ • rsync (http://rsync.samba.org/)
+
+ • Texi2HTML (http://www.nongnu.org/texi2html/)
+
+ Use version ‘1.82’. Later versions will not work.
+
+ Download ‘texi2html 1.82’ directly from:
+ <http://download.savannah.gnu.org/releases/texi2html/texi2html-1.82.tar.gz>;
+
+ Extract the files into an appropriate location and then run the
+ commands;
+
+ ./configure
+ make
+ sudo make install
+
+ Now verify that your operating system is able to see the correct
+ version of ‘texi2html’.
+
+ texi2html --version
+
+ • Fonts required to build the documentation in addition to those
+ required to run LilyPond:
+
+ gsfonts
+ fonts-linuxlibertine
+ fonts-liberation
+ fonts-dejavu
+ fonts-freefont-otf
+ ttf-bitstream-vera
+ texlive-fonts-recommended
+ ttf-xfree86-nonfree
+
+ Note: By default, when building LilyPond’s documentation,
+ ‘pdfTeX’ is be used. However ligatures (fi, fl, ff etc.) may
+ not be printed in the PDF output. In this case XeTeX can be
+ used instead. Download and install the ‘texlive-xetex’
+ package. The scripts used to build the LilyPond documentation
+ will use ‘XeTex’ instead of ‘pdfTex’ to generate the PDF
+ documents if it is available. No additional configuration is
+ required.
+
+1.3 Getting the source code
+===========================
+
+Downloading the Git repository
+------------------------------
+
+In general, developers compile LilyPond from within a local Git
+repository. Setting up a local Git repository is explained in *note
+(lilypond-contributor)Starting with Git::.
+
+Downloading a source tarball
+----------------------------
+
+Packagers are encouraged to use source tarballs for compiling.
+
+ The tarball for the latest stable release is available on the *note
+(lilypond-web)Source:: page.
+
+The latest source code snapshot
+(http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=snapshot) is also
+available as a tarball from the GNU Savannah Git server.
+
+All tagged releases (including legacy stable versions and the most
+recent development release) are available here:
+
+ <http://download.linuxaudio.org/lilypond/source/>
+
+ Download the tarball to your ‘~/src/’ directory, or some other
+appropriate place.
+
+ Note: Be careful where you unpack the tarball! Any
+ subdirectories of the current folder named ‘lilypond/’ or
+ ‘lilypond-X.Y.Z/’ (where X.Y.Z is the release number) will be
+ overwritten if there is a name clash with the tarball.
+
+ Unpack the tarball with this command:
+
+ tar -xzf lilypond-X.Y.Z.tar.gz
+
+ This creates a subdirectory within the current directory called
+‘lilypond-X.Y.Z/’. Once unpacked, the source files occupy about 40 MB
+of disk space.
+
+ Windows users wanting to look at the source code may have to download
+and install the free-software 7zip archiver (http://www.7-zip.org) to
+extract the tarball.
+
+1.4 Configuring ‘make’
+======================
+
+1.4.1 Running ‘./autogen.sh’
+----------------------------
+
+After you unpack the tarball (or download the Git repository), the
+contents of your top source directory should be similar to the current
+source tree listed at
+<http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=tree>.
+
+ Next, you need to create the generated files; enter the following
+command from your top source directory:
+
+ ./autogen.sh --noconfigure
+
+ This will generate a number of files and directories to aid
+configuration, such as ‘configure’, ‘README.txt’, etc.
+
+ Next, create the build directory with:
+
+ mkdir build/
+ cd build/
+
+ We heavily recommend building lilypond inside a separate directory
+with this method.
+
+1.4.2 Running ‘../configure’
+----------------------------
+
+Configuration options
+.....................
+
+ Note: make sure that you are in the ‘build/’ subdirectory of
+ your source tree.
+
+ The ‘../configure’ command (generated by ‘./autogen.sh’) provides
+many options for configuring ‘make’. To see them all, run:
+
+ ../configure --help
+
+Checking build dependencies
+...........................
+
+ Note: make sure that you are in the ‘build/’ subdirectory of
+ your source tree.
+
+ When ‘../configure’ is run without any arguments, it will check to
+make sure your system has everything required for compilation:
+
+ ../configure
+
+ If any build dependency is missing, ‘../configure’ will return with:
+
+ ERROR: Please install required programs: FOO
+
+ The following message is issued if you are missing programs that are
+only needed for building the documentation:
+
+ WARNING: Please consider installing optional programs: BAR
+
+ If you intend to build the documentation locally, you will need to
+install or update these programs accordingly.
+
+ Note: ‘../configure’ may fail to issue warnings for certain
+ documentation build requirements that are not met. If you
+ experience problems when building the documentation, you may
+ need to do a manual check of *note Requirements for building
+ documentation::.
+
+Configuring target directories
+..............................
+
+ Note: make sure that you are in the ‘build/’ subdirectory of
+ your source tree.
+
+ If you intend to use your local build to install a local copy of the
+program, you will probably want to configure the installation directory.
+Here are the relevant lines taken from the output of
+‘../configure --help’:
+
+ By default, ‘‘make install’’ will install all the files in
+ ‘/usr/local/bin’, ‘/usr/local/lib’ etc. You can specify an
+ installation prefix other than ‘/usr/local’ using ‘‘--prefix’’, for
+ instance ‘‘--prefix=$HOME’’.
+
+ A typical installation prefix is ‘$HOME/usr’:
+
+ ../configure --prefix=$HOME/usr
+
+ Note that if you plan to install a local build on a system where you
+do not have root privileges, you will need to do something like this
+anyway—‘make install’ will only succeed if the installation prefix
+points to a directory where you have write permission (such as your home
+directory). The installation directory will be automatically created if
+necessary.
+
+ The location of the ‘lilypond’ command installed by this process will
+be ‘PREFIX/bin/lilypond’; you may want to add ‘PREFIX/bin/’ to your
+‘$PATH’ if it is not already included.
+
+ It is also possible to specify separate installation directories for
+different types of program files. See the full output of
+‘../configure --help’ for more information.
+
+ If you encounter any problems, please see *note Problems::.
+
+1.5 Compiling LilyPond
+======================
+
+1.5.1 Using ‘make’
+------------------
+
+ Note: make sure that you are in the ‘build/’ subdirectory of
+ your source tree.
+
+ LilyPond is compiled with the ‘make’ command. Assuming ‘make’ is
+configured properly, you can simply run:
+
+ make
+
+ ‘make’ is short for ‘make all’. To view a list of ‘make’ targets,
+run:
+
+ make help
+
+ TODO: Describe what ‘make’ actually does.
+
+
+See also
+........
+
+ *note Generating documentation:: provides more info on the ‘make’
+targets used to build the LilyPond documentation.
+
+1.5.2 Saving time with the ‘-j’ option
+--------------------------------------
+
+If your system has multiple CPUs, you can speed up compilation by adding
+‘-jX’ to the ‘make’ command, where ‘X’ is one more than the number of
+cores you have. For example, a typical Core2Duo machine would use:
+
+ make -j3
+
+ If you get errors using the ‘-j’ option, and ‘make’ succeeds without
+it, try lowering the ‘X’ value.
+
+ Because multiple jobs run in parallel when ‘-j’ is used, it can be
+difficult to determine the source of an error when one occurs. In that
+case, running ‘make’ without the ‘-j’ is advised.
+
+1.5.3 Compiling for multiple platforms
+--------------------------------------
+
+If you want to build multiple versions of LilyPond with different
+configuration settings, you can use the ‘--enable-config=CONF’ option of
+‘configure’. You should use ‘make conf=CONF’ to generate the output in
+‘out-CONF’. For example, suppose you want to build with and without
+profiling, then use the following for the normal build
+
+ ./configure --prefix=$HOME/usr/ --enable-checking
+ make
+
+ and for the profiling version, specify a different configuration
+
+ ./configure --prefix=$HOME/usr/ --enable-profiling \
+ --enable-config=prof --disable-checking
+ make conf=prof
+
+ If you wish to install a copy of the build with profiling, don’t
+forget to use ‘conf=CONF’ when issuing ‘make install’:
+
+ make conf=prof install
+
+
+See also
+........
+
+ *note Installing LilyPond from a local build::
+
+1.5.4 Useful ‘make’ variables
+-----------------------------
+
+If a less verbose build output if desired, the variable ‘QUIET_BUILD’
+may be set to ‘1’ on ‘make’ command line, or in ‘local.make’ at top of
+the build tree.
+
+1.6 Post-compilation options
+============================
+
+1.6.1 Installing LilyPond from a local build
+--------------------------------------------
+
+If you configured ‘make’ to install your local build in a directory
+where you normally have write permission (such as your home directory),
+and you have compiled LilyPond by running ‘make’, you can install the
+program in your target directory by running:
+
+ make install
+
+ If instead, your installation directory is not one that you can
+normally write to (such as the default ‘/usr/local/’, which typically is
+only writeable by the superuser), you will need to temporarily become
+the superuser when running ‘make install’:
+
+ sudo make install
+
+or...
+
+ su -c 'make install'
+
+ If you don’t have superuser privileges, then you need to configure
+the installation directory to one that you can write to, and then
+re-install. See *note Configuring target directories::.
+
+1.6.2 Generating documentation
+------------------------------
+
+Documentation editor’s edit/compile cycle
+.........................................
+
+ • Initial documentation build:
+
+ make [-jX]
+ make [-jX CPU_COUNT=X] doc _## can take an hour or more_
+ make [-jX CPU_COUNT=X] doc-stage-1 _## to build only PDF documentation_
+
+ • Edit/compile cycle:
+
+ _## edit source files, then..._
+
+ make [-jX] _## needed if editing outside_
+ _## Documentation/, but useful anyway_
+ _## for finding Texinfo errors._
+ make [-jX CPU_COUNT=X] doc _## usually faster than initial build._
+
+ • Reset:
+
+ It is generally possible to remove the compiled documentation from
+ your system with ‘make doc-clean’, but this method is not 100%
+ guaranteed. Instead, if you want to be sure you have a clean
+ system, we recommend that you delete your ‘build/’ directory, and
+ begin compiling from scratch. Since the documentation compile
+ takes much longer than the non-documentation compile, this does not
+ increase the overall time by a great deal.
+
+Building documentation
+......................
+
+After a successful compile (using ‘make’), the documentation can be
+built by issuing:
+
+ make doc
+
+ or, to build only the PDF documentation and not the HTML,
+
+ make doc-stage-1
+
+ Note: The first time you run ‘make doc’, the process can
+ easily take an hour or more with not much output on the
+ command line.
+
+ After this initial build, ‘make doc’ only makes changes to the
+documentation where needed, so it may only take a minute or two to test
+changes if the documentation is already built.
+
+ If ‘make doc’ succeeds, the HTML documentation tree is available in
+‘out-www/offline-root/’, and can be browsed locally. Various portions
+of the documentation can be found by looking in ‘out/’ and ‘out-www’
+subdirectories in other places in the source tree, but these are only
+_portions_ of the docs. Please do not complain about anything which is
+broken in those places; the only complete set of documentation is in
+‘out-www/offline-root/’ from the top of the source tree.
+
+ ‘make doc’ sends the output from most of the compilation to logfiles.
+If the build fails for any reason, it should prompt you with the name of
+a logfile which will provide information to help you work out why the
+build failed. These logfiles are not deleted with ‘make doc-clean’. To
+remove all the logfiles generated by the compilation process, use:
+
+ make log-clean
+
+ ‘make doc’ compiles the documents for all languages. To save some
+compile time, the English language documents can be compiled on their
+own with:
+
+ make LANGS='' doc
+
+Similarly, it is possible to compile a subset of the translated
+documentation by specifying their language codes on the command line.
+For example, the French and German translations are compiled with:
+
+ make LANGS='de fr' doc
+
+Note that this will also compile the English version.
+
+ Compilation of documentation in Info format with images can be done
+separately by issuing:
+
+ make info
+
+An issue when switching branches between master and translation is the
+appearance/disappearance of translated versions of some manuals. If you
+see such a warning from make:
+
+ No rule to make target `X', needed by `Y'
+
+Your best bet is to delete the file Y.dep and to try again.
+
+Building a single document
+..........................
+
+It’s possible to build a single document. For example, to rebuild only
+‘contributor.pdf’, do the following:
+
+ cd build/
+ cd Documentation/
+ touch ../../Documentation/contributor.texi
+ make out=www out-www/contributor.pdf
+
+ If you are only working on a single document, test-building it in
+this way can give substantial time savings - recreating
+‘contributor.pdf’, for example, takes a matter of seconds.
+
+Saving time with ‘CPU_COUNT’
+............................
+
+The most time consuming task for building the documentation is running
+LilyPond to build images of music, and there cannot be several
+simultaneously running ‘lilypond-book’ instances, so the ‘-j’ ‘make’
+option does not significantly speed up the build process. To help speed
+it up, the makefile variable ‘CPU_COUNT’ may be set in ‘local.make’ or
+on the command line to the number of ‘.ly’ files that LilyPond should
+process simultaneously, e.g. on a bi-processor or dual core machine:
+
+ make -j3 CPU_COUNT=3 doc
+
+The recommended value of ‘CPU_COUNT’ is one plus the number of cores or
+processors, but it is advisable to set it to a smaller value unless your
+system has enough RAM to run that many simultaneous LilyPond instances.
+Also, values for the ‘-j’ option that pose problems with ‘make’ are less
+likely to pose problems with ‘make doc’ (this applies to both ‘-j’ and
+‘CPU_COUNT’). For example, with a quad-core processor, it is possible
+for ‘make -j5 CPU_COUNT=5 doc’ to work consistently even if ‘make -j5’
+rarely succeeds.
+
+AJAX search
+...........
+
+To build the documentation with interactive searching, use:
+
+ make doc AJAX_SEARCH=1
+
+ This requires PHP, and you must view the docs via a http connection
+(you cannot view them on your local filesystem).
+
+ Note: Due to potential security or load issues, this option is
+ not enabled in the official documentation builds. Enable at
+ your own risk.
+
+Installing documentation
+........................
+
+The HTML, PDF and if available Info files can be installed into the
+standard documentation path by issuing
+
+ make install-doc
+
+This also installs Info documentation with images if the installation
+prefix is properly set; otherwise, instructions to complete proper
+installation of Info documentation are printed on standard output.
+
+ To install the Info documentation separately, run:
+
+ make install-info
+
+Note that to get the images in Info documentation, ‘install-doc’ target
+creates symbolic links to HTML and PDF installed documentation tree in
+‘PREFIX/share/info’, in order to save disk space, whereas ‘install-info’
+copies images in ‘PREFIX/share/info’ subdirectories.
+
+ It is possible to build a documentation tree in
+‘out-www/online-root/’, with special processing, so it can be used on a
+website with content negotiation for automatic language selection; this
+can be achieved by issuing
+
+ make WEB_TARGETS=online doc
+
+and both ‘offline’ and ‘online’ targets can be generated by issuing
+
+ make WEB_TARGETS="offline online" doc
+
+ Several targets are available to clean the documentation build and
+help with maintaining documentation; an overview of these targets is
+available with
+
+ make help
+
+from every directory in the build tree. Most targets for documentation
+maintenance are available from ‘Documentation/’; for more information,
+see *note (lilypond-contributor)Documentation work::.
+
+ The makefile variable ‘QUIET_BUILD’ may be set to ‘1’ for a less
+verbose build output, just like for building the programs.
+
+Building documentation without compiling
+........................................
+
+The documentation can be built locally without compiling LilyPond
+binary, if LilyPond is already installed on your system.
+
+ From a fresh Git checkout, do
+
+ ./autogen.sh # ignore any warning messages
+ cp GNUmakefile.in GNUmakefile
+ make -C scripts && make -C python
+ nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond doc
+
+ Please note that this may break sometimes – for example, if a new
+feature is added with a test file in input/regression, even the latest
+development release of LilyPond will fail to build the docs.
+
+ You may build the manual without building all the ‘input/*’ stuff
+(i.e. mostly regression tests): change directory, for example to
+‘Documentation/’, issue ‘make doc’, which will build documentation in a
+subdirectory ‘out-www’ from the source files in current directory. In
+this case, if you also want to browse the documentation in its
+post-processed form, change back to top directory and issue
+
+ make out=www WWW-post
+
+
+Known issues and warnings
+.........................
+
+You may also need to create a script for ‘pngtopnm’ and ‘pnmtopng’. On
+GNU/Linux, I use this:
+
+export LD_LIBRARY_PATH=/usr/lib
+exec /usr/bin/pngtopnm "$@"
+
+ On MacOS X with fink, I use this:
+
+export DYLD_LIBRARY_PATH=/sw/lib
+exec /sw/bin/pngtopnm "$@"
+
+ On MacOS X with macports, you should use this:
+
+export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib
+exec /opt/local/bin/pngtopnm "$@"
+
+1.6.3 Testing LilyPond binary
+-----------------------------
+
+LilyPond comes with an extensive suite that exercises the entire
+program. This suite can be used to test that the binary has been built
+correctly.
+
+ The test suite can be executed with:
+
+make test
+
+ If the test suite completes successfully, the LilyPond binary has
+been verified.
+
+ More information on the regression test suite is found at *note
+(lilypond-contributor)Regression tests::.
+
+1.7 Problems
+============
+
+For help and questions use <lilypond-user@gnu.org>. Send bug reports to
+<bug-lilypond@gnu.org>.
+
+ Bugs that are not fault of LilyPond are documented here.
+
+Compiling on MacOS X
+--------------------
+
+Here are special instructions for compiling under MacOS X. These
+instructions assume that dependencies are installed using MacPorts.
+(http://www.macports.org/) The instructions have been tested using OS X
+10.5 (Leopard).
+
+ First, install the relevant dependencies using MacPorts.
+
+ Next, add the following to your relevant shell initialization files.
+This is ‘~/.profile’ by default. You should create this file if it does
+not exist.
+
+ export PATH=/opt/local/bin:/opt/local/sbin:$PATH
+ export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:$DYLD_FALLBACK_LIBRARY_PATH
+
+ Now you must edit the generated ‘config.make’ file. Change
+
+ FLEXLEXER_FILE = /usr/include/FlexLexer.h
+
+to:
+
+ FLEXLEXER_FILE = /opt/local/include/FlexLexer.h
+
+ At this point, you should verify that you have the appropriate fonts
+installed with your ghostscript installation. Check ‘ls
+/opt/local/share/ghostscript/fonts’ for: ’c0590*’ files (.pfb, .pfb and
+.afm). If you don’t have them, run the following commands to grab them
+from the ghostscript SVN server and install them in the appropriate
+location:
+
+ svn export http://svn.ghostscript.com/ghostscript/tags/urw-fonts-1.0.7pre44/
+ sudo mv urw-fonts-1.0.7pre44/* /opt/local/share/ghostscript/fonts/
+ rm -rf urw-fonts-1.07pre44
+
+ Now run the ‘./configure’ script. To avoid complications with
+automatic font detection, add
+
+ --with-fonts-dir=/opt/local/share/ghostscript/fonts
+
+Solaris
+-------
+
+Solaris7, ./configure
+
+ ‘./configure’ needs a POSIX compliant shell. On Solaris7, ‘/bin/sh’
+is not yet POSIX compliant, but ‘/bin/ksh’ or bash is. Run configure
+like
+
+ CONFIG_SHELL=/bin/ksh ksh -c ./configure
+
+or
+
+ CONFIG_SHELL=/bin/bash bash -c ./configure
+
+FreeBSD
+-------
+
+To use system fonts, dejaview must be installed. With the default port,
+the fonts are installed in ‘usr/X11R6/lib/X11/fonts/dejavu’.
+
+ Open the file ‘$LILYPONDBASE/usr/etc/fonts/local.conf’ and add the
+following line just after the ‘<fontconfig>’ line. (Adjust as necessary
+for your hierarchy.)
+
+ <dir>/usr/X11R6/lib/X11/fonts</dir>
+
+International fonts
+-------------------
+
+On Mac OS X, all fonts are installed by default. However, finding all
+system fonts requires a bit of configuration; see this post
+(http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html)
+on the ‘lilypond-user’ mailing list.
+
+ On Linux, international fonts are installed by different means on
+every distribution. We cannot list the exact commands or packages that
+are necessary, as each distribution is different, and the exact package
+names within each distribution changes. Here are some hints, though:
+
+Red Hat Fedora
+
+ taipeifonts fonts-xorg-truetype ttfonts-ja fonts-arabic \
+ ttfonts-zh_CN fonts-ja fonts-hebrew
+
+Debian GNU/Linux
+
+ apt-get install emacs-intl-fonts xfonts-intl-.* \
+ fonts-ipafont-gothic fonts-ipafont-mincho \
+ xfonts-bolkhov-75dpi xfonts-cronyx-100dpi xfonts-cronyx-75dpi
+
+Using lilypond python libraries
+-------------------------------
+
+If you want to use lilypond’s python libraries (either running certain
+build scripts manually, or using them in other programs), set
+‘PYTHONPATH’ to ‘python/out’ in your build directory, or
+‘.../usr/lib/lilypond/current/python’ in the installation directory
+structure.
+
+1.8 Concurrent stable and development versions
+==============================================
+
+It can be useful to have both the stable and the development versions of
+LilyPond available at once. One way to do this on GNU/Linux is to
+install the stable version using the precompiled binary, and run the
+development version from the source tree. After running ‘make all’ from
+the top directory of the LilyPond source files, there will be a binary
+called ‘lilypond’ in the ‘out’ directory:
+
+ <PATH TO>/lilypond/out/bin/lilypond
+
+ This binary can be run without actually doing the ‘make install’
+command. The advantage to this is that you can have all of the latest
+changes available after pulling from git and running ‘make all’, without
+having to uninstall the old version and reinstall the new.
+
+ So, to use the stable version, install it as usual and use the normal
+commands:
+
+ lilypond foobar.ly
+
+ To use the development version, create a link to the binary in the
+source tree by saving the following line in a file somewhere in your
+‘$PATH’:
+
+ exec <PATH TO>/lilypond/out/bin/lilypond "$@"
+
+ Save it as ‘Lilypond’ (with a capital L to distinguish it from the
+stable ‘lilypond’), and make it executable:
+
+ chmod +x Lilypond
+
+ Then you can invoke the development version this way:
+
+ Lilypond foobar.ly
+
+ TODO: ADD
+
+ - other compilation tricks for developers
+
+1.9 Build system
+================
+
+We currently use make and stepmake, which is complicated and only used
+by us. Hopefully this will change in the future.
+
+Version-specific texinfo macros
+-------------------------------
+
+ • made with ‘scripts/build/create-version-itexi.py’ and
+ ‘scripts/build/create-weblinks-itexi.py’
+
+ • used extensively in the ‘WEBSITE_ONLY_BUILD’ version of the website
+ (made with ‘website.make’, used on lilypond.org)
+
+ • not (?) used in the main docs?
+
+ • the numbers in VERSION file: MINOR_VERSION should be 1 more than
+ the last release, VERSION_DEVEL should be the last *online*
+ release. Yes, VERSION_DEVEL is less than VERSION.
+
projects / lilypond.git / blobdiff