![]() |
GNU LilyPondWelcome to the home of the GNU Music Typesetter |
|
INSTALL - compiling and installing GNU LilyPondObtainingYou can get the latest version of LilyPond at ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/. If you upgrade by patching do remember to rerun autoconf after applying the patch. If you do not want to download the entire archive for each version, the
safest method for upgrading is to use The following command produces xdelta patch lilypond-1.3.121-1.3.122.xd lilypond-1.3.121.tar.gz PrerequisitesFor compilation you need:
RunningGNU 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. Appropriate
Csh and sh scripts are left in 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 LilyPond is a big and slow program. A fast CPU and plenty of RAM is recommended for comfortable use. WebsiteThe website is the most convenient form to use for reading the documentation on-line documentation. It is made by entering make htmldocThis does require a functioning LilyPond. The binary doesn't have to be installed. If you want to auto-generate Lily's website, you'll need some additional conversion tools.
Configuring and compilingto 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/midi2ly.1 /usr/local/man/man1/abc2ly.1 /usr/local/man/man1/etf2ly.1 /usr/local/man/man1/convert-ly.1 /usr/local/man/man1/lilypond-book.1 /usr/local/man/man1/lilypond.1 /usr/local/bin/lilypond /usr/local/bin/midi2ly /usr/local/bin/convert-ly /usr/local/bin/lilypond-book /usr/local/bin/abc2ly /usr/local/bin/pmx2ly /usr/local/bin/musedata2ly /usr/local/bin/etf2ly /usr/local/share/lilypond/* /usr/local/share/locale/{....}/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
The configure script is Cygnus configure, and it will accept
./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 If you do make all everything will be compiled, but nothing will be installed. The
resulting binaries can be found in the subdirectories Configuring for multiple platformsIf you want to compile LilyPond with different configuration settings,
then, you can use the ./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=prof --enable-optimise --disable-checking make config=prof make config=prof install Installingif you have done a successful make install should do the trick. If you are doing an upgrade, please remember to remove obsolete
Red Hat LinuxRed Hat Linux users can compile an RPM. A spec file is in
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 Red Hat 7.0 i386 RPMS are available from ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/RedHat/. For compilation on a Red Hat system you need these packages, in addition to the those needed for running:
Debian GNU/LinuxA Debian package is also available. You may install it easily by using apt-get as root: apt-get install lilypond1.3 Alternatively, visit
You may contact Anthony Fok foka@debian.org for more information. The build scripts are in the subdirectory $ su - root # dpkg --purge lilypond lilypond1.3 # exit $ tar xzf lilypond-1.3.122.tar.gz $ cd lilypond-1.3.122 $ dch -p -v 1.3.122-0.local.1 "Local build." $ debuild $ su - root # dpkg -i ../lilypond1.3_1.3.122*.deb # exit $ For compilation on a Debian GNU/Linux system you need these packages, in addition to the those needed for running:
Most of these are listed on the Build-Depends line in the debian/control file. To ensure the creation of the lilypond deb is trouble-free, we recommend that you first install the following packages before starting dpkg-buildpackage by running apt-get as root. For Debian 2.2 (or 2.2r2, 2.2r3): apt-get install task-debian-devel task-c++-dev \ python-base libguile6-dev tetex-bin tetex-dev \ tetex-extra flex bison texinfo groff gs \ netpbm pnmtopng m4 gettext For Debian in development ("unstable", the future 2.3 or 3.0): apt-get install task-debian-devel task-c++-dev \ python-base libguile9-dev tetex-bin libkpathsea-dev \ tetex-extra flex bison texinfo bibtex2html groff gs \ netpbm pnmtopng m4 gettext And, just so that old fonts from previous versions of LilyPond won't interfere with your build, you may want to do this before the build too: dpkg --purge lilypond lilypond1.3 Windows NT/95Separate instructions on building for W32 are available; See the files
in ProblemsFor help and questions use help-gnu-music@gnu.org and gnu-music-discuss@gnu.org. Please consult the faq before mailing your problems. If you find bugs, please send bug reports to bug-gnu-music@gnu.org. Bugs that are LilyPond's fault are listed in our TODO list on the
web, or demonstrated in Bugs that are not LilyPond's fault are documented here. LinuxPPC Bugs:
Linux-i386
Solaris:
AIX
|
||
Go back to index of LilyPond.
Please send GNU LilyPond questions and comments to gnu-music-discuss@gnu.org. Please send comments on these web pages to (address unknown) Copyright (c) 1997, 1998, 1999, 2000 Han-Wen Nienhuys and Jan Nieuwenhuizen. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
|