(1.3), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
site}.
-@subsection source code
-
+@subsection Source code
If you want to compile LilyPond from source, download here:
@itemize @bullet
@uref{http://www.lilypond.org/ftp/} by HTTP.
@end itemize
+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, @file{.spec} files are included in the
+tarball; see instructions below.
+
@html
<a name="download-binaries">
@end html
-@subsection Binaries
+@subsection Precompiled binaries
+
+If you want to track bleeding edge development, try:
+
+@itemize @bullet
+@item @uref{ftp://ftp.debian.org/debian/pool/main/l/lilypond/, Debian
+GNU/Linux} usually has the latest binaries for the most useful stable
+and development versions, while
+@item @uref{http://rpmfind.net/linux/mandrake/cooker/contrib/RPMS/,
+Mandrake Cooker} also provides fairly recent versions.
+@end itemize
+
+Binaries are made available for other popular platforms, but as we need
+to compile them ourselves, they are not updated for every version
+released.
-Binaries are available, but are not updated for every version released.
@itemize @bullet
@item @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/RedHat/RPMS/, Red Hat i386}
-@item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc/, LinuxPPC}
-@item @uref{ftp://ftp.debian.org/debian/pool/main/l/lilypond/, Debian GNU/Linux}
+@item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/SuSE, SuSE}
+@item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc/,
+LinuxPPC}
@item
-@c @uref{http://home.austin.rr.com/jbr/jeff/lilypond/, Windows Stable}
-@c @item @uref{ftp://ftp.lilypond.org/pub/lilypond/gnu-windows, Windows
-@c Testing}
-@uref{http://www.lilypond.org/gnu-windows/, Windows Testing}
-
+@uref{http://www.lilypond.org/gnu-windows/, Windows}
@end itemize
@subsection Upgrading
@section Emacs mode
-An emacs mode for LilyPond is included with the source archive as
-@file{lilypond-mode.el} and @file{lilypond-font-lock.el}. If you have
-an RPM, it is in @file{/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 @file{lilypond-mode.el} and
+@file{lilypond-font-lock.el}. You should install these files somewhere
+in your @var{load-path}. If you have installed a precompiled LilyPond
+package, these files can be found in
+@file{/usr/share/doc/lilypond-x.y.z/}.
+
+Add this to your @file{~/.emacs} or @file{~/.emacs.el}, or install this
+file in Emacs' @file{site-start.d}:
+@example
+ ;;; lilypond-init.el --- Startup code for LilyPond mode
-Add this to your @file{~/.emacs} or @file{~/.emacs.el}:
-@example
(load-library "lilypond-mode.el")
(setq auto-mode-alist
(cons '("\\.ly$" . LilyPond-mode) auto-mode-alist))
@end example
If you have the latest LilyPond-1.4.x Debian package, LilyPond-mode is
-automatically loaded, so you need not modify your @code{~/.emacs} file.
+automatically loaded, you not even need to modify your @code{~/.emacs}
+file.
@section Compiling for distributions
@subsection Mandrake
Some binaries are available at rpmfind.net. Refer to
-@uref{ftp://ftp.rpmfind.net/linux/Mandrake-devel/cooker/contrib/RPMS/}.
+@uref{http://rpmfind.net/linux/mandrake/cooker/contrib/RPMS/}.
+You can also compile a RPM for Mandrake yourself. A spec file is in
+@file{make/out/lilypond.mandrake.spec}, see the instructions for building
+the Red Hat RPM.
@subsection Debian GNU/Linux
A Debian package is also available. You may install it easily by running
@command{apt-get} as root:
-
@example
+
apt-get install lilypond lilypond-doc
@end example
+You can also compile the .deb for Debian yourself, do:
+@example
+
+ apt-get -b source lilypond
+@end example
+
+If you're real impatient, you may even do:
+@example
+
+ cd lilypond-x.y.z # a previous version
+ uscan # download and build latest directly from upstream
+@end example
+
Debian's @TeX{} installation is a bit short on memory, you may want to
increase it like this:
Bugs that are not fault of LilyPond are documented here.
-@unnumberedsubsec Debian GNU/Linux unstable gcc-3.0
+@unnumberedsubsec 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:
-Flex (2.5.4a-11) in unstable does not produce g++-3.0 compliant C++
-code. To compile LilyPond with gcc-3.0 you may do:
@example
- CC=gcc-3.0 CXX=g++-3.0 ./configure
+ 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
@end example
+Note that this is fixed in Debian/unstable for flex >= 2.5.4a-13.
+
@unnumberedsubsec NetBSD
@itemize @bullet
projects / lilypond.git / blobdiff