-7/May/98 LilyPond 0.1.63 1
+13/May/98 LilyPond 0.1.64 1
compile. It's lot slower than most MusiXTeX
preprocessors)
+WEBSITE
+ If you want to auto-generate Lily's website, you'll need
+ some additional conversion tools.
+
+ o Xpmtoppm (from the libgr-progs package).
+
+ o Bib2html
+ (http://pertsserver.cs.uiuc.edu/~hull/bib2html.)
+ Which, in turn depends on Man2htlm
+ (http://askdonald.ask.uni-karlsruhe.de/
+ hppd/hpux/Networking/WWW/Man2html-1.05) for proper
+ installation (ugh). TeTeX users, don't forget to
+ rerun texhash.
+
CONFIGURING and COMPILING
to install GNU LilyPond, simply type:
CPPFLAGS are the preprocessor flags.
- the configure script is Cygnus configure, and it will
- accept --help. If you are not root, you will probably have
- to make it with
- configure --prefix=/home/me_myself_and_I/
- In this case, you will have to set MFINPUTS, and TEXINPUTS
- accordingly.
-
- If you want to install GNU LilyPond in /usr/local, and
- your TeX has no default hooks for local stuff (mine is
- broken too), you can do:
+13/May/98 LilyPond 0.1.64 2
-7/May/98 LilyPond 0.1.63 2
+INSTALL(1) LilyPond documentation INSTALL(1)
+ the configure script is Cygnus configure, and it will
+ accept --help. If you are not root, you will probably have
+ to make it with
+ configure --prefix=/home/me_myself_and_I/
-INSTALL(1) LilyPond documentation INSTALL(1)
+ In this case, you will have to set MFINPUTS, and TEXINPUTS
+ accordingly.
+ If you want to install GNU LilyPond in /usr/local, and
+ your TeX has no default hooks for local stuff (mine is
+ broken too), you can do:
configure --prefix=/usr/local --enable-tex-prefix=/usr/lib/texmf
Output to different configuration files. Needed for
multi-platform builds
- All options are documented in the configure help The
- option --enable-optimise is recommended for Real Life
- usage.
- If you do
- make all
- everything will be compiled, but nothing will be
- installed. The resulting binaries can be found in the
- subdirectories out/ (which contain all files generated
- during compilation).
+13/May/98 LilyPond 0.1.64 3
-7/May/98 LilyPond 0.1.63 3
+INSTALL(1) LilyPond documentation INSTALL(1)
+ All options are documented in the configure help The
+ option --enable-optimise is recommended for Real Life
+ usage.
+ If you do
-INSTALL(1) LilyPond documentation INSTALL(1)
+ make all
+ everything will be compiled, but nothing will be
+ installed. The resulting binaries can be found in the
+ subdirectories out/ (which contain all files generated
+ during compilation).
CONFIGURING FOR MULTIPLE PLATFORMS
If you want to compile LilyPond with different
EXAMPLE
This is what I type in my xterm:
- lilypond someinput.ly
- tex someinput.tex
- xdvi someinput&
- This is what the output looks like over here:
+13/May/98 LilyPond 0.1.64 4
+INSTALL(1) LilyPond documentation INSTALL(1)
+ lilypond someinput.ly
+ tex someinput.tex
+ xdvi someinput&
-
-7/May/98 LilyPond 0.1.63 4
-
-
-
-
-
-INSTALL(1) LilyPond documentation INSTALL(1)
-
+ This is what the output looks like over here:
GNU LilyPond 0.0.78 #4/FlowerLib 1.1.24 #0
Parsing ... [/home/hw/share/lilypond/init//
entire source tree is unpacked correctly, in particular
the empty out directories (flower/out, lib/out et. al.)
-AUTHORS
- Han-Wen Nienhuys <hanwen@cs.ruu.nl>
-
- Jan Nieuwenhuizen <jan@digicash.com>
-
-
-7/May/98 LilyPond 0.1.63 5
+13/May/98 LilyPond 0.1.64 5
INSTALL(1) LilyPond documentation INSTALL(1)
- Have fun!
-
-
-
+AUTHORS
+ Han-Wen Nienhuys <hanwen@cs.ruu.nl>
+ Jan Nieuwenhuizen <jan@digicash.com>
+ Have fun!
-7/May/98 LilyPond 0.1.63 6
+13/May/98 LilyPond 0.1.64 6