This document explains what you need to install LilyPond, and what you should do. If you are going to compile and install LilyPond often, e.g. when doing development, you might want to check out the buildscripts/set-lily.sh script. It sets some environment variables and symlinks, which comes in handly when you have to compile LilyPond more often.
You can get the latest version of LilyPond at ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/. Refer to the links document for mirror sites.
If you upgrade by patching do remember to rerun autoconf after applying the patch.
For compilation you need:
--disable-debugging
.
Although we recommend to use Unix, LilyPond is known to run on Windows NT/95/98 as well. See Section 11.
GNU LilyPond does use a lot of resources. For operation you need the following software
For running LilyPond successfully you have to help TeX and MetaFont find various files. The recommended way of doing so is adjusting the environment variables in the start-up scripts of your shell. An example is given here for the Bourne shell:
export MFINPUTS="/usr/local/share/lilypond/mf:" export TEXINPUTS="/usr/local/share/lilypond/tex:/usr/local/share/lilypond/ps:"The empty path component represents TeX and MetaFont's default search paths. Scripts with the proper paths for the bourne and C-shell respectively are generated in buildscripts/out/lilypond-profile and buildscripts/out/lilypond-login during compilation.
LilyPond is a hideously slow program. A fast CPU and plenty of RAM is recommended for comfortable use.
If you want to auto-generate Lily's website, you'll need some additional conversion tools.
The version of pnmtopng that is distributed with RedHat 5.1 and 5.2 contains a bug: pnmtopng is dynamically linked to the wrong version of libpng. Recompile it from source, and make sure that the pnmtopng binary is linked statically to the libpng that is included in libgr. RedHat 6.0 does not have this problem.
tar xzf libgr-2.0.13.tar.gz make cd png rm libpng.so* make pnmtopng
You can then install the new pnmtopng into /usr/local/bin/
The website will build without this utility, but you will not see our hypertextified bibliography.
TeTeX users should not forget to rerun texhash.
You also have to install buildscripts/out/ps-to-gifs in a directory that is in the path.
to install GNU LilyPond, simply type:
gunzip -c lilypond-x.y.z | tar xf - cd lilypond-x.y.z ./configure # fill in your standard prefix with --prefix make make install
This will install a number of files, something close to:
/usr/local/man/man1/mi2mu.1 /usr/local/man/man1/convert-mudela.1 /usr/local/man/man1/mudela-book.1 /usr/local/man/man1/lilypond.1 /usr/local/bin/lilypond /usr/local/bin/mi2mu /usr/local/share/lilypond/* /usr/local/share/locale/{it,nl}/LC_MESSAGES/lilypond.mo
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 your taste:
export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR" ./configure
CPPFLAGS
are the preprocessor flags.
The configure script is Cygnus configure, and it will accept --help. If you are not root, you will probably have to make it with a different --prefix option. Our favourite location is
./configure --prefix=$HOME/usr
In this case, you will have to set up MFINPUTS, and TEXINPUTS accordingly.
Since GNU LilyPond currently is beta, you are advised to also use
--enable-debugging --enable-checking
Options to configure include:
All options are documented in the configure help The option --enable-optimise is recommended for Real Life usage.
If you do
make all
everything will be compiled, but nothing will be installed. The resulting binaries can be found in the subdirectories out/ (which contain all files generated during compilation).
If you want to compile LilyPond with different configuration settings, then, you can use the --enable-config option. Example: suppose I want to build with and without profiling. Then I'd use the following for the normal build,
./configure --prefix=~ --disable-optimise --enable-checking make make install
and for the profiling version, I specify a different configuration.
./configure --prefix=~ --enable-profiling --enable-config=optprof --enable-optimise --disable-checking make config=optprof make config=optprof install
If you have done a successful make
, then a simple
make install
should do the trick.
If you are doing an upgrade, please remember to remove obsolete .pk and .tfm files of the fonts. A script has been provided to do the work for you, see bin/clean-fonts.sh.
This is what I type in my xterm:
lilypond someinput.ly tex someinput.tex xdvi someinput&
This is what the output looks like over here:
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 ... [14][25] Postprocessing elements... TeX output to someinput.tex ... Creating MIDI elements ...MIDI output to someinput.midi ... hw:~/musix/spacer$ xdvi someinput& [1] 855
Check out the input files, some of them have comments Please refer to the man page for more information.
RedHat Linux users can compile an RPM. A spec file is in make/out/lilypond.spec, it is distributed along with the sources.
You can make the rpm by issuing
rpm -tb lilypond-x.y.z.tar.gz rpm -i /usr/src/redhat/RPMS/i386/lilypond-x.y.z
Precompiled i386 RedHat RPMS are available from http://linux.umbc.edu/software/lilypond/rpms/.
A Debian package is also available; contact Anthony Fok foka@debian.org. The build scripts are in the subdirectory debian/.
Separate instructions on building for W32 are avaible in the file README-W32.yo.
Have fun!
Please send GNU LilyPond questions and comments to gnu-music-discuss@gnu.org.
Please send comments on these web pages to
(address unknown),
send other FSF & GNU inquiries and questions to
Copyright (c) 1997, 1998, 1999 Han-Wen Nienhuys and Jan Nieuwenhuizen.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.