X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=INSTALL.txt;h=7fa5e4fe7ccffb7859c1dce59d6def02372f8f46;hb=5f68ba5ca0edd64f0f6723e65c27993c2dfb1e96;hp=eb9e4038159f520293ce9eac988c15eadaef2bde;hpb=70a98a1bfe6eafa9a4cee14a8a5264a52a329d03;p=lilypond.git diff --git a/INSTALL.txt b/INSTALL.txt index eb9e403815..7fa5e4fe7c 100644 --- a/INSTALL.txt +++ b/INSTALL.txt @@ -8,8 +8,8 @@ Table of Contents INSTALL - compiling and installing GNU LilyPond Downloading - source code - Binaries + Source code + Precompiled binaries Upgrading Requirements Compilation @@ -26,7 +26,7 @@ INSTALL - compiling and installing GNU LilyPond Mandrake Debian GNU/Linux Problems - Debian GNU/Linux unstable gcc-3.0 + FLex-2.5.4a and gcc-3.0 NetBSD Solaris: AIX @@ -49,7 +49,7 @@ version (1.2) reside on the GNU servers 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: @@ -62,21 +62,39 @@ source code * 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: - Binaries are available, but are not updated for every version + * 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 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 --------- @@ -142,15 +160,6 @@ Compilation (ftp://ftp.ctan.org/tex-archive/macros/latex/contrib/supported/geometry). This package is normally included with the TeX distribution. - * MetaPost, needed for generating PostScript fonts. Please note that - tetex-0.4pl8 (included with Red Hat 5.x) does not include - `mfplain.mp', which is needed for producing the scalable font - files. - - If you don't have MetaPost and don't want to use PostScript - output, then edit `mf/GNUmakefile', removing the line saying - `PFA_FILES='. - * kpathsea, a library for searching (TeX) files. `kpathsea' is usually included with your installation of TeX. You may need to install a tetex-devel or tetex-dev package too. @@ -163,6 +172,23 @@ Compilation ./configure --without-kpathsea --enable-tfm-path=/usr/share/texmf/fonts/tfm/public/cm/:/usr/share/texmf/fonts/tfm/ams/symbols + * pktrace, [OPTIONAL], needed for generating PostScript Type1 fonts. + Get it from + `http://www.cs.uu.nl/~hanwen/public/software/pktrace-0.1.tar.gz' + + * autotrace-0.27a, [OPTIONAL], needed for generating PostScript Type1 + fonts. You must apply the patch included pktrace-0.1 first. + `http://autotrace.sourceforge.net'. + + * MetaPost [OPTIONAL] needed for generating PostScript Type3 fonts. + Please note that tetex-0.4pl8 (included with Red Hat 5.x) does not + include `mfplain.mp', which is needed for producing the scalable + font files. + + If you don't have MetaPost and don't want to use PostScript + output, then edit `mf/GNUmakefile', removing the line saying + `PFA_FILES='. + Running requirements -------------------- @@ -270,18 +296,24 @@ profiling. Then I'd use the following for the normal build, 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 =========================== @@ -308,13 +340,6 @@ addition to the those needed for running: glibc-devel, gcc-c++, libstdc++-devel, guile-devel, flex, bison, texinfo, tetex-devel, groff, libgr-progs. - Warning - - There appears to be a problem with the Xdvi shipped with Red Hat 7.1. -Symptoms: Xdvi responds very sluggishly or hangs while viewing lilypond -output. The cause for this problem is unknown; you are advised to -recompile Xdvi from source. - LinuxPPC -------- @@ -350,7 +375,11 @@ Mandrake -------- 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 ---------------- @@ -360,6 +389,15 @@ running `apt-get' as root: 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 @@ -450,8 +488,9 @@ by running \`apt-get' as root before building the package: 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 \ + apt-get install binutils cpp gcc libc6-dev \ + g++ libstdc++2.10-dev \ + python-base libguile-dev tetex-bin libkpathsea-dev \ tetex-extra flex bison texinfo bibtex2html groff gs \ netpbm m4 gettext @@ -463,23 +502,25 @@ interfere with your build, you may want to do this before the build too: Problems ======== - For help and questions use and -. Please consult the FAQ before mailing -your problems. If you find bugs, please send bug reports to -. + For help and questions use . Please consult +the FAQ before mailing your problems. If you find bugs, please send +bug reports to . Bugs that are not fault of LilyPond are documented here. -Debian GNU/Linux unstable gcc-3.0 ---------------------------------- +FLex-2.5.4a and gcc-3.0 +----------------------- - 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: - CC=gcc-3.0 CXX=g++-3.0 ./configure + 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 ------