3 INSTALL - installing GNU LilyPond
7 This page documents installation and compilation of GNU LilyPond
11 if you have downloaded a
15 version, then this is version is I<not> meant for producing nice
16 output, but to keep your patchsets up to date. It might not even compile.
20 For compilation you need.
26 Unix. GNU LilyPond is known to run on Linux, AIX, Digital Unix and
29 If you have the Cygnus WIN32 port of the GNU utils, it will
30 even work in Lose NT/95, but don't promise to support it.
34 GNU C++ v2.7 or better, with libg++ installed. Version 2.7.2
35 or better recommended. I almost positive that it will not compile with
44 Flex (2.5.1 or better).
48 Bison. (Version 1.25 or better)
58 Perl. Most scripts are written in Perl. The documentation was created
59 with the perl's Plain Old Documentation.
68 =head1 CONFIGURING and COMPILING
70 to install GNU LilyPond, simply type:
75 This will install the following files:
77 /usr/local/man/man1/lilypond.1
78 /usr/local/lib/libflower.{so,a}
79 /usr/local/bin/lilypond
81 /usr/local/share/lilypond/*
82 /usr/lib/texmf/texmf/tex/lilypond/*
84 The TeX include directory is detected dynamically, but it can be
85 adjusted with B<--enable-tex-prefix> and B<--enable-tex-dir>. The
86 above assumes that you are root and have the gnu development tools,
87 and your make is gnu make. If this is not the case, you can adjust
88 your environment variables to your taste:
90 export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR"
93 C<CPPFLAGS> are the preprocessor flags.
95 the configure script is Cygnus configure, and it will accept
96 B<--help>. If you are not root, you will probably have to make it with
98 configure --prefix=/home/me_myself_and_I/
100 In this case, you will have to set MFINPUTS, and TEINPUTS accordingly.
102 If you want to install GNU LilyPond in F</usr/local>, and your TeX has
103 no default hooks for local stuff (mine is broken too), you can do:
105 configure --prefix=/usr/local --enable-tex-prefix=/usr/lib/texmf
107 Since GNU LilyPond currently is beta, you are advised to also use
112 other options include:
121 All options are documented in the F<configure> help
122 The option B<--enable-optimise> is recommended for Real Life usage.
128 everything will be compiled, but nothing will be installed. The
129 resulting binaries can be found in the subdirectory
134 If you have done a successful C<make>, then a simple
142 Install the musixtex fonts in a directory which TeX and MF knows (if
143 you are root, look for a directory which contains the directories with
144 AMS and CM source (*.mf) files. Create a subdir lilypond or musixtex
145 and copy the fonts into that). Do not forget to rehash TeX (if
148 Example: my fonts are in F</usr/local/lib/texfonts/musixtex/>, and I
149 have a symlink pointing to that in
150 F</usr/lib/texmf/texmf/fonts/source/public/>
160 The -O2 option to gcc triggers a gcc bug on DEC Alpha in dstream.cc. You
161 should turn off this flag for this file.
167 GNU LilyPond does use a lot of resources. For operation you need the following:
174 A fast computer (a full page of music typically takes 1 minute
175 on my 486/66, using the B<--enable-checking> compile. It's lot slower
176 than most MusiXTeX preprocessors)
184 The MusixTeX fonts. (I use those found in MusixTeX T.59). Beware, the
185 clef symbol has changed position in recent versions of MusixTeX)
189 Please refer to the man page for more information.
193 RedHat Linux users should be able to get a RPM. A spec file is in
194 F<make/lilypond.spec>. You should be able to create an rpm as a normal
195 user. Be sure you have a ~/.rpmrc, and edit the RPM-dir in
203 you need the cygnus win32 gnu port development stuff; have a look
204 at http://www.cygnus.com/gnu-win32.
206 to make GNU LilyPond under, brr, aargh, well, simply type:
213 GNU LilyPond (pl 0.0.39) is known to compile on the following platforms:
215 * linux 2.0.x, g++ 2.7.2[.1]
217 * windows-nt 4.0, cygnus gnu-win32 beta17.1 (~=g++ 2.7.2)
218 * linux 2.0.28 X to doze, gcc-go32 (~=g++ 2.7.2) [exec. untested]
222 Han-Wen Nienhuys <hanwen@stack.nl>
224 Jan Nieuwenhuizen <jan@digicash.com>