3 INSTALL - installing GNU LilyPond
7 This page documents installation and compilation of GNU LilyPond
11 For compilation you need.
17 A Unix system with GNU tools. GNU LilyPond is known to run on these
18 unices: Linux, AIX, Digital Unix and Solaris.
20 If you have the Cygnus WINDOWS32 port of the GNU utils, it will even
21 work in Windows NT/95, but don't promise to support it.
25 GNU C++ v2.7 or better, with libg++ installed. Version 2.7.2
26 or better recommended.
34 Flex (2.5.1 or better).
38 Bison. (Version 1.25 or better)
44 GNU LilyPond does use a lot of resources. For operation you need the following:
55 The MusixTeX fonts (I included those found in MusixTeX T.73). Beware,
56 the clef symbol seems to have changed its position in some versions,
57 (notably Egler's, a.k.a. OpusTeX). The MusixTeX fonts are included in
58 MusixTeX T.73, which can be had from any CTAN site, eg at
60 ftp://ftp.shsu.edu/tex-archive/macros/musixtex/taupin
61 ftp://ftp.tex.ac.uk/tex-archive/macros/musixtex/taupin
62 ftp://ftp.dante.de/tex-archive/macros/musixtex/taupin
64 You only need the contents of the F<mf/> subdirectory of the package.
68 Although not strictly necessary, these are recommended to have.
74 Perl. Most scripts are written in Perl. The documentation was created
75 with the perl's Plain Old Documentation.
84 A fast computer (a full page of music typically takes 1 minute
85 on my 486/133, using the B<--enable-checking> compile. It's lot slower
86 than most MusiXTeX preprocessors)
91 =head1 CONFIGURING and COMPILING
93 to install GNU LilyPond, simply type:
98 This will install the following files:
100 /usr/local/man/man1/mi2mu.1
101 /usr/local/man/man5/mudela.5
102 /usr/local/man/man1/lilypond.1
103 /usr/local/lib/libflower.{so,a}
104 /usr/local/bin/lilypond
106 /usr/local/share/lilypond/*
107 /usr/lib/texmf/texmf/tex/lilypond/*
109 The TeX include directory is detected dynamically, but it can be
110 adjusted with B<--enable-tex-prefix> and B<--enable-tex-dir>. The
111 above assumes that you are root and have the gnu development tools,
112 and your make is gnu make. If this is not the case, you can adjust
113 your environment variables to your taste:
115 export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR"
118 C<CPPFLAGS> are the preprocessor flags.
120 the configure script is Cygnus configure, and it will accept
121 B<--help>. If you are not root, you will probably have to make it with
123 configure --prefix=/home/me_myself_and_I/
125 In this case, you will have to set MFINPUTS, and TEXINPUTS accordingly.
127 If you want to install GNU LilyPond in F</usr/local>, and your TeX has
128 no default hooks for local stuff (mine is broken too), you can do:
130 configure --prefix=/usr/local --enable-tex-prefix=/usr/lib/texmf
132 Since GNU LilyPond currently is beta, you are advised to also use
137 other options include:
141 =item --enable-shared
143 Make a shared library (gnu/linux, solaris (?) only )
145 =item --enable-printing
147 Enable debugging print routines (lilypond B<-d> option)
149 =item --enable-optimise
151 Set maximum optimisation
153 =item --enable-profiling
155 Compile with support for profiling
157 =item --enable-tex-prefix
159 Set the directory where texmf lives
161 =item --enable-tex-dir
163 Set then directory tex input is in (detected as a subdir of tex-prefix)
165 =item --enable-mf-dir
167 Set then directory mf input is in (idem)
171 All options are documented in the F<configure> help
172 The option B<--enable-optimise> is recommended for Real Life usage.
178 everything will be compiled, but nothing will be installed. The
179 resulting binaries can be found in the subdirectories F<out/> (which
180 contain all files generated during compilation).
185 If you have done a successful C<make>, then a simple
191 Install the musixtex fonts in a directory which TeX and MF knows (if
192 you are root, look for a directory which contains the directories with
193 AMS and CM source (*.mf) files. Create a subdir lilypond or musixtex
194 and copy the fonts into that). Do not forget to rehash TeX (if
197 Example: my fonts are in F</usr/local/lib/texfonts/musixtex/>, and I
198 have a symlink pointing to that in
199 F</usr/lib/texmf/texmf/fonts/source/public/>. After I copied the
200 files, I ran "texhash"
202 ftp://hprib.lps.u-psud.fr/pub/music_zips/musixtex.zip
212 The -O2 option to gcc triggers a gcc bug on DEC Alpha in dstream.cc. You
213 should turn off this flag for this file.
219 This is what I type in my xterm:
221 lilypond someinput.ly
225 This is what the output looks like over here:
227 hw:~/musix/spacer$ lilypond input/kortjakje.ly
228 GNU LilyPond 0.0.71 #20/FlowerLib 1.1.20 #0
229 Parsing ... [/home/hw/share/lilypond/init//symbol.ini <..snip..>
230 .. .ini]][input/kortjakje.ly]
231 Creating elements ...
232 Preprocessing elements...
233 Calculating column positions ... [3][8][13][17][21][25]
234 Postprocessing elements...
235 TeX output to lelie.tex ...
237 hw:~/musix/spacer$ tex lelie
238 This is TeX, Version 3.14159 (C version 6.1)
240 Hyphenation patterns for english, dutch, german, loaded.
241 (/home/hw/lib/texmf/tex/lilypond/lilyponddefs.tex) [1] )
242 Output written on lelie.dvi (1 page, 8944 bytes).
243 Transcript written on lelie.log.
245 hw:~/musix/spacer$ xdvi lelie&
248 Check out the input files, some of them have comments
249 Please refer to the man page for more information.
253 RedHat Linux users should be able to get a RPM. A spec file is in
254 F<make/out/lilypond.spec>. You should be able to create an rpm as a normal
255 user. Be sure you have a ~/.rpmrc, and edit the RPM-dir in
256 F<Variables.make>. (If you create the RPM as a normal user the
257 permissions will not be set correctly, unfortunately)
264 you need the cygnus windows32 gnu port development stuff; have a look
265 at http://www.cygnus.com/gnu-win32.
267 to make GNU LilyPond under, brr, aargh, well, simply type:
274 Han-Wen Nienhuys <hanwen@stack.nl>
276 Jan Nieuwenhuizen <jan@digicash.com>