o A GNU system: GNU LilyPond is known to run on these
GNU systems: Linux (PPC, intel), FreeBSD, AIX,
- NeXTStep, Digital Unix and Solaris.
+ NeXTStep, IRIX, 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
don't promise to support it.
- o GNU C++ v2.7 or better, with libg++ installed.
- Version 2.7.2 or better recommended.
-
- o GNU make.
-
- o Flex (2.5.1 or better).
-
- o Bison. (Version 1.25 or better)
+ o GNU C++ version 2.7 or newer (yes, 2.8 is fine).
RUNNING
GNU LilyPond does use a lot of resources. For operation
Although not strictly necessary, these are recommended to
have.
- o Perl-5. Most documentation was created with the
+ o GNU make.
+
+ o Flex (version 2.5.4 or newer).
+
+ o Bison (version 1.25 or newer). =item *
+
+ Perl-5. Most documentation was created with the
perl's Plain Old Documentation. (I use 5.003)
-28/Jan/98 LilyPond 0.1.46 1
+
+21/Apr/98 LilyPond 0.1.58 1
-28/Jan/98 LilyPond 0.1.46 2
+21/Apr/98 LilyPond 0.1.58 2
--enable-mf-dir
Set the directory mf input is in (idem)
- --enable-out-dir
- Set the directory for machine generated output.
-
All options are documented in the configure help The
option --enable-optimise is recommended for Real Life
usage.
subdirectories out/ (which contain all files generated
during compilation).
- Building for multiple hosts
-
- LilyPond does not follow the GNU standards when it comes
- to configuring and making Makefiles. In LilyPond, make
- generates all output in output directories (called out/,
- by default). You can have multiple compiles from the same
- source-tree, by overriding the setting for the output
- directory.
-
-
-
-28/Jan/98 LilyPond 0.1.46 3
-
-
-
+INSTALLING
+ If you have done a successful make, then a simple
+ make install
-INSTALL(1) LilyPond documentation INSTALL(1)
+ should do the trick.
+ If you are doing an upgrade, please remember to remove
+ obsolete .pk and .tfm files of the fonts. A script has
+ been provided to do the work, see bin/clean-fonts.sh.
- Example: on my system, I do debugging and lots compiling.
- For this I use the configuration as follows:
- configure --prefix=~ --enable-debugging --enable-printing --enable-checking
- make all
- and I want to do profiling. For that I use
- configure --prefix=~ --enable-debugging --disable-printing\
- --disable-checking --enable-profiling --enable-optimise\
- --enable-out-dir=out-profile
+21/Apr/98 LilyPond 0.1.58 3
- make OUTDIR_NAME=out-profile all
- These two commands build two entirely separate versions of
- LilyPond. In Real Life, you would probably also want to
- have two different prefixes. On my machine this is no
- problem; I never do make install. My prefix dirs are
- linked back to my source directory.
-INSTALLING
- If you have done a successful make, then a simple
- make install
- should do the trick.
+INSTALL(1) LilyPond documentation INSTALL(1)
- If you are doing an upgrade, please remember to remove
- obsolete .pk and .tfm files of the fonts. A script has
- been provided to do the work, see bin/clean-fonts.sh.
CAVEATS
o The -O2 option to gcc triggers a gcc bug on DEC Alpha
This is what the output looks like over here:
-
-
-
-
-
-
-
-
-
-28/Jan/98 LilyPond 0.1.46 4
-
-
-
-
-
-INSTALL(1) LilyPond documentation INSTALL(1)
-
-
GNU LilyPond 0.0.78 #4/FlowerLib 1.1.24 #0
Parsing ... [/home/hw/share/lilypond/init//
<..etc..>
http://www.cygnus.com/gnu-win32.
To make GNU LilyPond under, brr, aargh, shudder...
+
+
+
+21/Apr/98 LilyPond 0.1.58 4
+
+
+
+
+
+INSTALL(1) LilyPond documentation INSTALL(1)
+
+
windows32, well, simply type:
bash configure
them, but anyway, here are the installation instructions
for those deprecated fonts.
-
-
-28/Jan/98 LilyPond 0.1.46 5
-
-
-
-
-
-INSTALL(1) LilyPond documentation INSTALL(1)
-
-
[obsolete] I use the MusixTeX fonts those found in
MusixTeX T.73. Beware, the clef symbol seems to have
changed its position in some versions, (notably Egler's,
a.k.a. OpusTeX). The MusixTeX fonts are included in
- MusixTeX (T73 or better), which can be had from any CTAN
+ MusixTeX (T73 or newer), which can be had from any CTAN
site, e.g. at
ftp://ftp.shsu.edu/tex-archive/macros/musixtex/taupin
the fonts, so you have to edit the definitions in
tex/eglerdefs.tex.
+
+
+
+
+21/Apr/98 LilyPond 0.1.58 5
+
+
+
+
+
+INSTALL(1) LilyPond documentation INSTALL(1)
+
+
AUTHORS
- Han-Wen Nienhuys <hanwen@stack.nl>
+ Han-Wen Nienhuys <hanwen@cs.ruu.nl>
Jan Nieuwenhuizen <jan@digicash.com>
-28/Jan/98 LilyPond 0.1.46 6
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+21/Apr/98 LilyPond 0.1.58 6
projects / lilypond.git / blobdiff