P\bP\bP\bPR\bR\bR\bRE\bE\bE\bER\bR\bR\bRE\bE\bE\bEQ\bQ\bQ\bQU\bU\bU\bUI\bI\bI\bIS\bS\bS\bSI\bI\bI\bIT\bT\bT\bTE\bE\bE\bES\bS\bS\bS
For compilation you need.
- +\bo A Unix system with GNU tools. GNU LilyPond is known
- to run on these unices: Linux, AIX, Digital Unix and
- Solaris.
+ +\bo A GNU system: GNU LilyPond is known to run on these
+ GNU systems: Linux, AIX, Digital Unix and Solaris.
If you have the Cygnus WINDOWS32 port of the GNU
utils, it will even work in Windows NT/95, but we
ftp://ftp.shsu.edu/tex-archive/macros/musixtex/taupin
+ ftp://ftp.tex.ac.uk/tex-archive/macros/musixtex/taupin
-8/Aug/97 LilyPond 0.1.14 1
+20/Oct/97 LilyPond 0.1.24 1
INSTALL(1) LilyPond documentation INSTALL(1)
- ftp://ftp.tex.ac.uk/tex-archive/macros/musixtex/taupin
-
ftp://ftp.dante.de/tex-archive/macros/musixtex/taupin
You only need the contents of the _\bm_\bf_\b/
Although not strictly necessary, these are recommended to
have.
- +\bo Perl-5. Most scripts are written in Perl. Most
- documentation was created with the perl's Plain
- Old Documentation. (I use 5.003)
+ +\bo Perl-5. Most documentation was created with the
+ perl's Plain Old Documentation. (I use 5.003)
+
+ +\bo Python. Although perl is nice, python is
+ better. We will shift towards python for build
+ scripts
+\bo GNU find
d\bd\bd\bdi\bi\bi\bir\br\br\br. The above assumes that you are root and have the GNU
development tools, and your make is GNU make. If this is
not the case, you can adjust your environment variables to
- your taste:
-8/Aug/97 LilyPond 0.1.14 2
+20/Oct/97 LilyPond 0.1.24 2
INSTALL(1) LilyPond documentation INSTALL(1)
+ your taste:
+
export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR"
configure
--enable-mf-dir
Set the directory mf input is in (idem)
- [obsolete]
-
-8/Aug/97 LilyPond 0.1.14 3
+20/Oct/97 LilyPond 0.1.24 3
-8/Aug/97 LilyPond 0.1.14 4
+20/Oct/97 LilyPond 0.1.24 4
-8/Aug/97 LilyPond 0.1.14 5
+20/Oct/97 LilyPond 0.1.24 5
-8/Aug/97 LilyPond 0.1.14 6
+20/Oct/97 LilyPond 0.1.24 6