--*-text-*-
+This is the toplevel README to LilyPond -*-Text-*-
-last update: 96/12/12, 0.0.16
-INTRODUCTION
+LilyPond is the GNU Project music typesetter. The program generates
+visual or auditive output from a music definition file: it can typeset
+formatted sheet music to a TeX file and play (mechanical) performances
+to a MIDI file. Features include multiple staffs, meters, clefs,
+keys, lyrics, versatile input-language, cadenzas, beams, slurs,
+triplets.
-This is a beta version of LilyPond (a music typesetter). Please send
-your helpful comments and patches to me,
- hanwen@stack.nl
+1. VERSIONING
-LilyPond is updated very frequently, the latest version is always available at:
+if you have downloaded a
- ftp://pcnov095.win.tue.nl/pub/lilypond
+ *.pre*
-PREREQUISITES
+version, then this is version is *not* meant for producing nice output
+(but to keep your patchsets up to date). It might not even compile.
-Compilation:
- - Unix (any decent Linux distrib is fine)
- - GNU C++ v2.7 or better
- - GNU make.
- - flex
- - bison/yacc
- - The "flower" library
- - which should be available from the same source you got this from.
+2. REQUIREMENTS
-Operation:
+For the compilation and running of LilyPond you need some additional
+packages. The most unusual one of this are the metafont sources to
+MusixTeX-fonts. Please refer to the installation instructions on how
+to obtain and install them.
- - TeX
- - the MusixTeX fonts
-The Makefile uses perl for trivial
-operations, and you could tinker with it to use sed or awk.
+3. INSTALLATION
-COMPILING
+For your convenience, a formatted copy of the INSTALL instructions are
+in the toplevel directory, as INSTALL.text
-Do:
- tar zxf flower-1.11.9.tar.gz
- mv flower-1.11.9 flower
- cd flower; make; cd ..
- tar zxf lilypond-1.2.13.tar.gz
- cd lilypond-1.2.13
- make
+4. DOCUMENTATION
-why G++ >= 2.7? LilyPond & flower lib uses:
+The real documentation is the directory Documentation/
- builtin bool
- typeof
- operator <?, operator >?
+To generate the pretty-printed docs, you have to run configure first,
+and then do this:
-USING
+ make doc
-No, you shouldn't. Really. If you're still not discouraged; this is
-what I type in my xterm:
+You can also simply read the .pod sources. They are ASCII text.
+.pod is the documentation format of perl (see perlpod(1))
- lilypond maartje.ly
- tex test
- xdvi test&
-This is what the output looks like over here.
+5. COMMENTS
-hw:~/musix/spacer$ lilypond maartje.ly
-LilyPond version 0.0.16 compiled on Dec 11 1996 at 13:54:27
-Parsing ... [symbol.ini][maartje.ly]
-Processing ... Calculating ... Postprocessing ...
-output to lelie.uit...
+LilyPond is a long way from finished and polished. I do appreciate
+criticism, comments, bugreports, patches, etc. Please send e-mail to
+the mailing lists. See Documentation/links.pod for more info
-hw:~/musix/spacer$ tex test
-This is TeX, Version 3.14159 (C version 6.1)
-(test.tex
-Hyphenation patterns for english, dutch, loaded.
-(lilyponddefs.tex) (lelie.uit) [1] [2] )
-Output written on test.dvi (2 pages, 8072 bytes).
-Transcript written on test.log.
-hw:~/musix/spacer$ xdvi test&
-[1] 1468
+6. DOZE
-PROBLEMS
+If you have received this file as part of a DOS/Window32 distribution
+(lilypond-*.zip), then it is advisable to also download the source
+package, since it might contain more documentation
-If LilyPond bombs out, then please recompile using -g, and send a gdb
-stacktrace of the crash.
+ ftp://pcnov095.win.tue.nl/pub/lilypond/ (Europe)
+ ftp://alpha.gnu.org/gnu/lilypond/ (US)
+The website also contains the complete documentation
-HOW DOES IT WORK
+ http://www.stack.nl/~hanwen/lilypond/index.html
-* Use The Source, Luke. If you don't know C++, you can try editing
-.dstreamrc for copious debugging output. (use -d)
+If you decide to build LilyPond from source, please read the INSTALL
+document first, especially the Windows NT/95 section.
-* the subdir Documentation/ contains some more-in-depth matter on LilyPond
+7. CAVEATS
-* The source is commented in the DOC++ style.
-Check out doc++ at
+* Please read the file BUGS for some ugly bugs. This especially applies
+Linux-Intel unix users.
- http://www.ZIB-Berlin.DE/VisPar/doc++/doc++.html
+* If you have installed a previous version, be sure to remove old font
+files, eg
+
+ rm `find /var/lib/texmf/fonts -name 'feta*'`
+
+a script to do this for you is in bin/cleanfonts.sh