INSTALL - installing GNU LilyPond
D\bD\bD\bDE\bE\bE\bES\bS\bS\bSC\bC\bC\bCR\bR\bR\bRI\bI\bI\bIP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bN
- This page documents installation and compilation of GNU
+ This page documents installation and compilation of GNU
LilyPond
-I\bI\bI\bIM\bM\bM\bMP\bP\bP\bPO\bO\bO\bOR\bR\bR\bRT\bT\bT\bTA\bA\bA\bAN\bN\bN\bNT\bT\bT\bT
- if you have downloaded a
+A\bA\bA\bAB\bB\bB\bBS\bS\bS\bST\bT\bT\bTR\bR\bR\bRA\bA\bA\bAC\bC\bC\bCT\bT\bT\bT
+ You do something which looks remotely like
- *.pre*
+ configure
+ make
+ make install
+ tar -C /usr/lib/texmf/fonts/source/ -zxf musixtex-T73.tgz 'mf/*'
+
+ The detailed instructions follow here.
- version, then this is version is _\bn_\bo_\bt meant for producing
- nice output, but to keep your patchsets up to date. It
- might not even compile.
P\bP\bP\bPR\bR\bR\bRE\bE\bE\bER\bR\bR\bRE\bE\bE\bEQ\bQ\bQ\bQU\bU\bU\bUI\bI\bI\bIS\bS\bS\bSI\bI\bI\bIT\bT\bT\bTE\bE\bE\bES\bS\bS\bS
For compilation you need.
- +\bo A Unix system with GNU tools. GNU LilyPond is known
- to run on Linux, AIX, Digital Unix and Solaris.
+ +\bo A GNU system: GNU LilyPond is known to run on these
+ GNU systems: Linux, AIX, Digital Unix and Solaris.
If you have the Cygnus WINDOWS32 port of the GNU
- utils, it will even work in Lose NT/95, but don't
- promise to support it.
+ utils, it will even work in Windows NT/95, but we
+ don't promise to support it.
+\bo GNU C++ v2.7 or better, with libg++ installed.
- Version 2.7.2 or better recommended. I almost
- positive that it will not compile with AT&T CC.
+ Version 2.7.2 or better recommended.
+\bo GNU make.
+\bo Bison. (Version 1.25 or better)
-R\bR\bR\bRE\bE\bE\bEC\bC\bC\bCO\bO\bO\bOM\bM\bM\bMM\bM\bM\bME\bE\bE\bEN\bN\bN\bND\bD\bD\bDE\bE\bE\bED\bD\bD\bD
- +\bo Perl. Most scripts are written in Perl. The
- documentation was created with the perl's Plain Old
- Documentation.
+R\bR\bR\bRU\bU\bU\bUN\bN\bN\bNN\bN\bN\bNI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
+ GNU LilyPond does use a lot of resources. For operation
+ you need the following:
- +\bo (GNU) find
+ +\bo TeX
-C\bC\bC\bCO\bO\bO\bON\bN\bN\bNF\bF\bF\bFI\bI\bI\bIG\bG\bG\bGU\bU\bU\bUR\bR\bR\bRI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG a\ba\ba\ban\bn\bn\bnd\bd\bd\bd C\bC\bC\bCO\bO\bO\bOM\bM\bM\bMP\bP\bP\bPI\bI\bI\bIL\bL\bL\bLI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
- to install GNU LilyPond, simply type:
+ +\bo The MusixTeX fonts (I included those found in
+ MusixTeX T.73). Beware, the clef symbol seems to have
+ changed its position in some versions, (notably
+ Egler's, a.k.a. OpusTeX). The MusixTeX fonts are
+ included in MusixTeX (T73 or better), which can be
+ had from any CTAN site, e.g. at
- configure
- make install
+ ftp://ftp.shsu.edu/tex-archive/macros/musixtex/taupin
- This will install the following files:
+ ftp://ftp.tex.ac.uk/tex-archive/macros/musixtex/taupin
+20/Oct/97 LilyPond 0.1.24 1
-28/May/97 LilyPond 0.0.66 1
+INSTALL(1) LilyPond documentation INSTALL(1)
+ ftp://ftp.dante.de/tex-archive/macros/musixtex/taupin
-INSTALL(1) LilyPond documentation INSTALL(1)
+ You only need the contents of the _\bm_\bf_\b/
+ subdirectory of the package. The primary site of
+ the Taupin version is ftp://hprib.lps.u-
+ psud.fr/pub/music_zips/musixtex.zip
+
+ Andreas Egler's version of MusixTeX, now called
+ OpusTeX, will also work. Andreas moved some
+ characters around in the fonts, so you have to
+ edit the definitions in tex/eglerdefs.tex (patch
+ appreciated)
+
+R\bR\bR\bRE\bE\bE\bEC\bC\bC\bCO\bO\bO\bOM\bM\bM\bMM\bM\bM\bME\bE\bE\bEN\bN\bN\bND\bD\bD\bDE\bE\bE\bED\bD\bD\bD
+ Although not strictly necessary, these are recommended to
+ have.
+ +\bo Perl-5. Most documentation was created with the
+ perl's Plain Old Documentation. (I use 5.003)
+
+ +\bo Python. Although perl is nice, python is
+ better. We will shift towards python for build
+ scripts
+
+ +\bo GNU find
+
+ +\bo A fast computer (a full page of music typically
+ takes 1 minute on my 486/133, using the
+ -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-c\bc\bc\bch\bh\bh\bhe\be\be\bec\bc\bc\bck\bk\bk\bki\bi\bi\bin\bn\bn\bng\bg\bg\bg compile. It's lot slower than
+ most MusiXTeX preprocessors)
+
+C\bC\bC\bCO\bO\bO\bON\bN\bN\bNF\bF\bF\bFI\bI\bI\bIG\bG\bG\bGU\bU\bU\bUR\bR\bR\bRI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG a\ba\ba\ban\bn\bn\bnd\bd\bd\bd C\bC\bC\bCO\bO\bO\bOM\bM\bM\bMP\bP\bP\bPI\bI\bI\bIL\bL\bL\bLI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
+ to install GNU LilyPond, simply type:
+
+ configure
+ make install
+
+ This will install the following files:
/usr/local/man/man1/mi2mu.1
- /usr/local/man/man5/mudela.5
+ /usr/local/man/man1/convert-mudela.1
+ /usr/local/man/man1/mudela-book.1
/usr/local/man/man1/lilypond.1
/usr/local/lib/libflower.{so,a}
/usr/local/bin/lilypond
/usr/local/bin/mi2mu
/usr/local/share/lilypond/*
/usr/lib/texmf/texmf/tex/lilypond/*
- /usr/lib/texmf/texmf/fonts/source/lilypond/*
The TeX include directory is detected dynamically, but it
can be adjusted with -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-t\bt\bt\bte\be\be\bex\bx\bx\bx-\b-\b-\b-p\bp\bp\bpr\br\br\bre\be\be\bef\bf\bf\bfi\bi\bi\bix\bx\bx\bx and -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-t\bt\bt\bte\be\be\bex\bx\bx\bx-\b-\b-\b-
- d\bd\bd\bdi\bi\bi\bir\br\br\br. The above assumes that you are root and have the gnu
- development tools, and your make is gnu make. If this is
+ d\bd\bd\bdi\bi\bi\bir\br\br\br. The above assumes that you are root and have the GNU
+ development tools, and your make is GNU make. If this is
not the case, you can adjust your environment variables to
+
+
+
+20/Oct/97 LilyPond 0.1.24 2
+
+
+
+
+
+INSTALL(1) LilyPond documentation INSTALL(1)
+
+
your taste:
export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR"
configure --prefix=/home/me_myself_and_I/
- In this case, you will have to set MFINPUTS, and TEINPUTS
+ In this case, you will have to set MFINPUTS, and TEXINPUTS
accordingly.
If you want to install GNU LilyPond in _\b/_\bu_\bs_\br_\b/_\bl_\bo_\bc_\ba_\bl, and
other options include:
--enable-shared
- Make a shared library (linux, solaris (?) only )
+ Make a shared library (gnu/linux, solaris (?)
+ only )
--enable-printing
- Enable debugging print routines (lilypond -\b-\b-\b-d\bd\bd\bd option)
+ Enable debugging print routines (lilypond -\b-\b-\b-d\bd\bd\bd
+ option)
--enable-optimise
- Set maximum optimisation
+ Set maximum optimisation: compile with -\b-\b-\b-O\bO\bO\bO2\b2\b2\b2
+
+ --enable-profiling
+ Compile with support for profiling
+ --enable-tex-prefix
+ Set the directory where TeX and Metafont live
+
+ --enable-tex-dir
+ Set then directory TeX input is in (detected as a
+ subdir of tex-prefix)
+
+ --enable-mf-dir
+ Set the directory mf input is in (idem)
-28/May/97 LilyPond 0.0.66 2
+
+20/Oct/97 LilyPond 0.1.24 3
INSTALL(1) LilyPond documentation INSTALL(1)
- --enable-profiling
- Compile with support for profiling
+ --enable-out-dir
+ Set the directory for machine generated output.
- --enable-tex-prefix
- Set the directory where texmf lives
+ All options are documented in the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be help
+ The option -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bim\bm\bm\bmi\bi\bi\bis\bs\bs\bse\be\be\be is recommended for
+ Real Life usage.
- --enable-tex-dir
- Set then directory tex input is in (detected as a
- subdir of tex-prefix)
+ If you do
- --enable-mf-dir
- Set then directory tex input is in (idem)
+ make all
+
+ everything will be compiled, but nothing will be
+ installed. The resulting binaries can be found
+ in the subdirectories _\bo_\bu_\bt_\b/ (which contain all
+ files generated during compilation).
- All options are documented in the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be help The
- option -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bim\bm\bm\bmi\bi\bi\bis\bs\bs\bse\be\be\be is recommended for Real Life
- usage.
+ B\bB\bB\bBu\bu\bu\bui\bi\bi\bil\bl\bl\bld\bd\bd\bdi\bi\bi\bin\bn\bn\bng\bg\bg\bg f\bf\bf\bfo\bo\bo\bor\br\br\br m\bm\bm\bmu\bu\bu\bul\bl\bl\blt\bt\bt\bti\bi\bi\bip\bp\bp\bpl\bl\bl\ble\be\be\be h\bh\bh\bho\bo\bo\bos\bs\bs\bst\bt\bt\bts\bs\bs\bs
- If you do
+ LilyPond does not follow the GNU standards when it comes
+ to configuring and making Makefiles. In LilyPond, _\bm_\ba_\bk_\be
+ generates _\ba_\bl_\bl output in output directories (called _\bo_\bu_\bt_\b/,
+ by default). You can have multiple compiles from the same
+ source-tree, by overriding the setting for the output
+ directory.
+ Example: on my system, I do debugging and lots compiling.
+ For this I use the configuration as follows:
+
+ configure --prefix=~ --enable-debugging --enable-printing --enable-checking
make all
- everything will be compiled, but nothing will be
- installed. The resulting binaries can be found in the
- subdirectories _\bo_\bu_\bt_\b/ (which contain all files generated
- during compilation).
+ and I want to do profiling. For that I use
+
+ configure --prefix=~ --enable-debugging --disable-printing\
+ --disable-checking --enable-profiling --enable-optimise\
+ --enable-out-dir=out-profile
+
+ make OUTDIR_NAME=out-profile all
+
+ These two commands build two entirely separate versions of
+ LilyPond. In Real Life, you would probably also want to
+ have two different prefixes. On my machine this is no
+ problem; I never do make install. My prefix dirs are
+ linked back to my source directory.
I\bI\bI\bIN\bN\bN\bNS\bS\bS\bST\bT\bT\bTA\bA\bA\bAL\bL\bL\bLL\bL\bL\bLI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
If you have done a successful make, then a simple
should do the trick.
- [todo. Obsolete; fonts are in distribution now.]
-
Install the musixtex fonts in a directory which TeX and MF
knows (if you are root, look for a directory which
- contains the directories with AMS and CM source (*.mf)
- files. Create a subdir lilypond or musixtex and copy the
- fonts into that). Do not forget to rehash TeX (if
- applicable)
-
- Example: my fonts are in
- _\b/_\bu_\bs_\br_\b/_\bl_\bo_\bc_\ba_\bl_\b/_\bl_\bi_\bb_\b/_\bt_\be_\bx_\bf_\bo_\bn_\bt_\bs_\b/_\bm_\bu_\bs_\bi_\bx_\bt_\be_\bx_\b/, and I have a symlink
- pointing to that in
- _\b/_\bu_\bs_\br_\b/_\bl_\bi_\bb_\b/_\bt_\be_\bx_\bm_\bf_\b/_\bt_\be_\bx_\bm_\bf_\b/_\bf_\bo_\bn_\bt_\bs_\b/_\bs_\bo_\bu_\br_\bc_\be_\b/_\bp_\bu_\bb_\bl_\bi_\bc_\b/
-
-C\bC\bC\bCA\bA\bA\bAV\bV\bV\bVE\bE\bE\bEA\bA\bA\bAT\bT\bT\bTS\bS\bS\bS
- +\bo The -O2 option to gcc triggers a gcc bug on DEC Alpha
- in dstream.cc. You should turn off this flag for this
- file.
-
-R\bR\bR\bRU\bU\bU\bUN\bN\bN\bNN\bN\bN\bNI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
- GNU LilyPond does use a lot of resources. For operation
-28/May/97 LilyPond 0.0.66 3
+20/Oct/97 LilyPond 0.1.24 4
INSTALL(1) LilyPond documentation INSTALL(1)
- you need the following:
+ contains the directories with AMS and CM source (*.mf)
+ files. Create a subdir lilypond or musixtex and copy the
+ fonts into that). Do not forget to rehash TeX (if
+ applicable)
- +\bo A fast computer (a full page of music typically takes
- 1 minute on my 486/66, using the -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-c\bc\bc\bch\bh\bh\bhe\be\be\bec\bc\bc\bck\bk\bk\bki\bi\bi\bin\bn\bn\bng\bg\bg\bg
- compile. It's lot slower than most MusiXTeX
- preprocessors)
+ Example: my fonts are in
+ _\b/_\bu_\bs_\br_\b/_\bl_\bo_\bc_\ba_\bl_\b/_\bl_\bi_\bb_\b/_\bt_\be_\bx_\bf_\bo_\bn_\bt_\bs_\b/_\bm_\bu_\bs_\bi_\bx_\bt_\be_\bx_\b/, and I have a symlink
+ pointing to that in
+ _\b/_\bu_\bs_\br_\b/_\bl_\bi_\bb_\b/_\bt_\be_\bx_\bm_\bf_\b/_\bt_\be_\bx_\bm_\bf_\b/_\bf_\bo_\bn_\bt_\bs_\b/_\bs_\bo_\bu_\br_\bc_\be_\b/_\bp_\bu_\bb_\bl_\bi_\bc_\b/. After I copied
+ the files, I ran "texhash"
- +\bo TeX
+C\bC\bC\bCA\bA\bA\bAV\bV\bV\bVE\bE\bE\bEA\bA\bA\bAT\bT\bT\bTS\bS\bS\bS
+ +\bo The -O2 option to gcc triggers a gcc bug on DEC
+ Alpha in dstream.cc. You should turn off this
+ flag for this file.
- +\bo The MusixTeX fonts. (I use those found in MusixTeX
- T.59). Beware, the clef symbol has changed position
- in recent versions of MusixTeX)
+ +\bo Perl5.003 and Perl5.004 use different syntax for
+ pod2html:
- At this time, GNU LilyPond output looks nice, but is not
- of production quality. If you're not discouraged; this is
- what I type in my xterm:
+E\bE\bE\bEX\bX\bX\bXA\bA\bA\bAM\bM\bM\bMP\bP\bP\bPL\bL\bL\bLE\bE\bE\bE
+ This is what I type in my xterm:
lilypond someinput.ly
tex lelie.tex
This is what the output looks like over here:
- hw:~/musix/spacer$ GNU LilyPond 0.0.60 #8/FlowerLib 1.1.14 #2
- Parsing ... [./input/kortjakje.ly[lots of stuff]]
- Setting up requests...Processing requests ...[8][16][24][25]
+ GNU LilyPond 0.0.78 #4/FlowerLib 1.1.24 #0
+ Parsing ... [/home/hw/share/lilypond/init//
+ <..etc..>
+ init//performer.ly]]][input/kortjakje.ly]
+ Creating elements ...[8][16][24][25]
Preprocessing elements...
- Calculating column positions ... [3][7][12][16][20][25]
+ Calculating column positions ... [14][25]
Postprocessing elements...
TeX output to lelie.tex ...
-
- hw:~/musix/spacer$ tex lelie
- This is TeX, Version 3.14159 (C version 6.1)
- (lelie.tex
- Hyphenation patterns for english, dutch, german, loaded.
- (/home/hw/lib/texmf/tex/lilypond/lilyponddefs.tex) [1] )
- Output written on lelie.dvi (1 page, 8944 bytes).
- Transcript written on lelie.log.
+ Creating MIDI elements ...MIDI output to lelie.midi ...
hw:~/musix/spacer$ xdvi lelie&
[1] 855
R\bR\bR\bRE\bE\bE\bED\bD\bD\bDH\bH\bH\bHA\bA\bA\bAT\bT\bT\bT L\bL\bL\bLI\bI\bI\bIN\bN\bN\bNU\bU\bU\bUX\bX\bX\bX
RedHat Linux users should be able to get a RPM. A spec
- file is in _\bm_\ba_\bk_\be_\b/_\bl_\bi_\bl_\by_\bp_\bo_\bn_\bd_\b._\bs_\bp_\be_\bc. You should be able to
+ file is in _\bm_\ba_\bk_\be_\b/_\bo_\bu_\bt_\b/_\bl_\bi_\bl_\by_\bp_\bo_\bn_\bd_\b._\bs_\bp_\be_\bc. You should be able to
create an rpm as a normal user. Be sure you have a
- ~/.rpmrc, and edit the RPM-dir in _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs_\b._\bm_\ba_\bk_\be
+ ~/.rpmrc, and edit the RPM-dir in _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs_\b._\bm_\ba_\bk_\be. (If you
+ create the RPM as a normal user the permissions will not
+ be set correctly, unfortunately)
-W\bW\bW\bWI\bI\bI\bIN\bN\bN\bND\bD\bD\bDO\bO\bO\bOZ\bZ\bZ\bZE\bE\bE\bE
- Windows NT:
-28/May/97 LilyPond 0.0.66 4
+20/Oct/97 LilyPond 0.1.24 5
INSTALL(1) LilyPond documentation INSTALL(1)
- you need the cygnus windows32 gnu port development stuff;
- have a look at http://www.cygnus.com/gnu-win32.
+D\bD\bD\bDE\bE\bE\bEB\bB\bB\bBI\bI\bI\bIA\bA\bA\bAN\bN\bN\bN G\bG\bG\bGN\bN\bN\bNU\bU\bU\bU/\b/\b/\b/L\bL\bL\bLI\bI\bI\bIN\bN\bN\bNU\bU\bU\bUX\bX\bX\bX
+ A Debian package is in the works
- to make GNU LilyPond under, brr, aargh, well, simply type:
+W\bW\bW\bWI\bI\bI\bIN\bN\bN\bND\bD\bD\bDO\bO\bO\bOW\bW\bW\bWS\bS\bS\bS N\bN\bN\bNT\bT\bT\bT/\b/\b/\b/9\b9\b9\b95\b5\b5\b5
+ So, you're stuck with Windows, eh? Well, don't worry, you
+ just need (to get) Cygnus' windows32 port of gnu
+ development stuff; have a look at
+ http://www.cygnus.com/gnu-win32.
+
+ To make GNU LilyPond under, brr, aargh, shudder...
+ windows32, well, simply type:
bash configure
- make win32
+ make
-P\bP\bP\bPL\bL\bL\bLA\bA\bA\bAT\bT\bT\bTF\bF\bF\bFO\bO\bO\bOR\bR\bR\bRM\bM\bM\bMS\bS\bS\bS
- GNU LilyPond (pl 0.0.39) is known to compile on the
- following platforms:
+A\bA\bA\bAU\bU\bU\bUT\bT\bT\bTH\bH\bH\bHO\bO\bO\bOR\bR\bR\bRS\bS\bS\bS
+ Han-Wen Nienhuys <hanwen@stack.nl>
+
+ Jan Nieuwenhuizen <jan@digicash.com>
+
+ Have fun!
- Unix:
- * linux 2.0.x, g++ 2.7.2[.1]
- * aix 4.1, g++ 2.7.2
- Other:
- * windows-nt 4.0, cygnus gnu-windows32 beta17.1 (~=g++ 2.7.2)
- * linux 2.0.28 X to doze, gcc-go32 (~=g++ 2.7.2) [exec. untested]
-A\bA\bA\bAU\bU\bU\bUT\bT\bT\bTH\bH\bH\bHO\bO\bO\bOR\bR\bR\bRS\bS\bS\bS
- Han-Wen Nienhuys <hanwen@stack.nl>
- Jan Nieuwenhuizen <jan@digicash.com>
- Have fun!
-28/May/97 LilyPond 0.0.66 5
+20/Oct/97 LilyPond 0.1.24 6
projects / lilypond.git / blobdiff