You do something which looks remotely like
configure # Check out the buildscripts/set-lily.sh script make make install
The detailed instructions follow here. The buildscripts/set-lily.sh script sets some environment variables and symlinks, which comes in handly when you have to compile LilyPond very often. It is aimed at people who run (or debug) LilyPond without installing.
For compilation you need:
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:
Although not strictly necessary, these are recommended to have.
If you want to auto-generate Lily's website, you'll need some additional conversion tools.
TeTeX users should not forget to rerun texhash.
to install GNU LilyPond, simply type:
configure --enable-tex-dir=XXXX --enable-mf-dir=YYYY 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 /usr/lib/texmf/texmf/tex/lilypond/*
You should specify directories that are in TeX's and MetaFont's include path with the options (--enable-tex-dir) and --enable-mf-dir. If you don't specify any directories, the TeX include directory is detected dynamically, which is unreliable. 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.
If you want to install GNU LilyPond in /usr/local, and your TeX has no default hooks for local stuff, you can do:
configure --prefix=/usr/local --enable-tex-prefix=/usr/lib/texmf
Since GNU LilyPond currently is beta, you are advised to also use
--enable-debugging --enable-checking
Other options 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 configuration=optprof make configuration=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. You should install a gif file called lelie_icon.gif along with the sources. You can generate this gif file by typing
make gifs
in the directory Documentation.
You can make the rpm by issuing
make rpm
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!