INSTALL - compiling and installing GNU LilyPond
Downloading
- source code
- Binaries
+ Source code
+ Precompiled binaries
Upgrading
Requirements
Compilation
Mandrake
Debian GNU/Linux
Problems
+ FLex-2.5.4a and gcc-3.0
NetBSD
Solaris:
AIX
latest odd numbered version (1.3), whose webpages are on the lilypond
site (http://www.lilypond.org/).
-source code
+Source code
-----------
If you want to compile LilyPond from source, download here:
* at `lilypond.org' `ftp://ftp.lilypond.org/pub/LilyPond/' by FTP and
`http://www.lilypond.org/ftp/' by HTTP.
-Binaries
---------
+ Of course, if your platform supports LilyPond, such as Debian
+GNU/Linux, FreeBSD, OpenBSD or NetBSD, you're encouraged to use the
+native build from source drill.
+
+ For Red Hat Linux and SuSE Linux, `.spec' files are included in the
+tarball; see instructions below.
+
+Precompiled binaries
+--------------------
+
+ If you want to track bleeding edge development, try:
+
+ * Debian GNU/Linux
+ (ftp://ftp.debian.org/debian/pool/main/l/lilypond/) usually has
+ the latest binaries for the most useful stable and development
+ versions, while
+
+ * Mandrake Cooker
+ (http://rpmfind.net/linux/mandrake/cooker/contrib/RPMS/) also
+ provides fairly recent versions.
- Binaries are available, but are not updated for every version
+ Binaries are made available for other popular platforms, but as we
+need to compile them ourselves, they are not updated for every version
released.
+
* Red Hat i386
(ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/RedHat/RPMS/)
- * LinuxPPC (ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc/)
-
- * Debian GNU/Linux
- (ftp://ftp.debian.org/debian/pool/main/l/lilypond/)
+ * SuSE (ftp://ftp.lilypond.org/pub/LilyPond/binaries/SuSE)
- * Windows Testing (http://www.lilypond.org/gnu-windows/)
+ * LinuxPPC (ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc/)
+ * Windows (http://www.lilypond.org/gnu-windows/)
Upgrading
---------
Emacs mode
==========
- An emacs mode for LilyPond is included with the source archive as
-`lilypond-mode.el' and `lilypond-font-lock.el'. If you have an RPM, it
-is in `/usr/share/doc/lilypond-X/'. You have to install it yourself.
+ An Emacs mode for entering music and running LilyPond is included
+with the source archive as `lilypond-mode.el' and
+`lilypond-font-lock.el'. You should install these files somewhere in
+your LOAD-PATH. If you have installed a precompiled LilyPond package,
+these files can be found in `/usr/share/doc/lilypond-x.y.z/'.
- Add this to your `~/.emacs' or `~/.emacs.el':
+ Add this to your `~/.emacs' or `~/.emacs.el', or install this file
+in Emacs' `site-start.d':
+ ;;; lilypond-init.el --- Startup code for LilyPond mode
+
(load-library "lilypond-mode.el")
(setq auto-mode-alist
(cons '("\\.ly$" . LilyPond-mode) auto-mode-alist))
(add-hook 'LilyPond-mode-hook (lambda () (turn-on-font-lock)))
If you have the latest LilyPond-1.4.x Debian package, LilyPond-mode
-is automatically loaded, so you need not modify your `~/.emacs' file.
+is automatically loaded, you not even need to modify your `~/.emacs'
+file.
Compiling for distributions
===========================
`ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/'.
You can also compile them yourself. A spec file is in
-`make/out/redhat.spec'. This file is distributed along with the
-sources. You can make the rpm by issuing
+`make/out/lilypond.redhat.spec'. This file is distributed along with
+the sources. You can make the rpm by issuing
tar xfz lilypond-x.y.z.tar.gz
- rpm -bb lilypond-x.y.z/make/out/redhat.spec
+ rpm -bb lilypond-x.y.z/make/out/lilypond.redhat.spec
rpm -i /usr/src/redhat/RPMS/i386/lilypond-x.y.z
For running on a Red Hat system you need these packages: guile,
Some LinuxPPC RPMS should available from
`ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/'.
- A LinuxPPC RPM can be made using the `redhat.spec' file.
+ A LinuxPPC RPM can be made using the `lilypond.redhat.spec' file.
SuSE
----
Some SUSE RPMS should available from
-`ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/'.
+`ftp://ftp.lilypond.org/pub/LilyPond/binaries/SuSE'.
You can also compile a RPM for SUSE yourself. A spec file is in
-`make/out/suse.spec', see the instructions for building the Red Hat RPM.
+`make/out/lilypond.suse.spec', see the instructions for building the
+Red Hat RPM.
You must have the following packages: guile tcsh tetex te_latex
te_kpath te_mpost libpng python gpp libgpp gettext autoconf netpbm
--------
Some binaries are available at rpmfind.net. Refer to
-`ftp://ftp.rpmfind.net/linux/Mandrake-devel/cooker/contrib/RPMS/'.
+`http://rpmfind.net/linux/mandrake/cooker/contrib/RPMS/'.
+
+ You can also compile a RPM for Mandrake yourself. A spec file is in
+`make/out/lilypond.mandrake.spec', see the instructions for building
+the Red Hat RPM.
Debian GNU/Linux
----------------
apt-get install lilypond lilypond-doc
+ You can also compile the .deb for Debian yourself, do:
+
+ apt-get -b source lilypond
+
+ If you're real impatient, you may even do:
+
+ cd lilypond-x.y.z # a previous version
+ uscan # download and build latest directly from upstream
+
Debian's TeX installation is a bit short on memory, you may want to
increase it like this:
--- /etc/texmf/texmf.cnf.dpkg Sun Jan 28 14:12:14 2001
Problems
========
- For 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>.
+ For help and questions use <lilypond-user@gnu.org>. Please consult
+the FAQ before mailing your problems. If you find bugs, please send
+bug reports to <bug-lilypond@gnu.org>.
Bugs that are not fault of LilyPond are documented here.
+FLex-2.5.4a and gcc-3.0
+-----------------------
+
+ Flex 2.5.4a does not produce g++-3.0 compliant C++ code. To compile
+LilyPond with gcc-3.0 you may do:
+
+ CC=gcc-3.0 CXX=g++-3.0 ./configure --enable-config=gcc-3.0
+ make conf=gcc-3.0 -C lily out-gcc-3.0/lexer.cc
+ patch -p1 < lexer-gcc-3.0.patch
+ make conf=gcc-3.0 -C lily
+
+ Note that this is fixed in Debian/unstable for flex >= 2.5.4a-13.
+
NetBSD
------
projects / lilypond.git / blobdiff