X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=INSTALL.txt;h=e69de29bb2d1d6434b8b29ae775ad8c2e48c5391;hb=5626b34b525c4979eec5e9461a4560d9cdd5b36d;hp=6c7ee5ec6a1399378109fe17cea8fa40b17e49de;hpb=c844072722a39a5fcd20372b0497d9130bd41dd7;p=lilypond.git diff --git a/INSTALL.txt b/INSTALL.txt index 6c7ee5ec6a..e69de29bb2 100644 --- a/INSTALL.txt +++ b/INSTALL.txt @@ -1,396 +0,0 @@ - - - -INSTALL(1) LilyPond documentation INSTALL(1) - - -NAME - INSTALL - installing GNU LilyPond - -DESCRIPTION - This page documents installation and compilation of GNU - LilyPond - -ABSTRACT - You do something which looks remotely like - - configure - make - make install - - The detailed instructions follow here. - -PREREQUISITES - For compilation you need. - - o A GNU system: GNU LilyPond is known to run on these - GNU systems: Linux (PPC, intel), FreeBSD, AIX, - 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++ version 2.7 or newer (yes, 2.8 is fine). - - o Python - -RUNNING - GNU LilyPond does use a lot of resources. For operation - you need the following: - - o TeX - - o A PostScript printer and/or viewer (such as - Ghostscript) is strongly recommended. Xdvi will show - all embedded PostScript too if you have Ghostscript - installed. - -RECOMMENDED - Although not strictly necessary, these are recommended to - have. - - o GNU make. - - o Flex (version 2.5.4 or newer). - - o Bison (version 1.25 or newer). - - o Perl-5. Most documentation was created with the - perl's Plain Old Documentation. (I use 5.003) - - - -7/May/98 LilyPond 0.1.63 1 - - - - - -INSTALL(1) LilyPond documentation INSTALL(1) - - - o Python. Although perl is nice, python is better. We - will shift towards python for build scripts - - o GNU find - - o A fast computer (a full page of music typically takes - 1 minute on my 486/133, using the --enable-checking - compile. It's lot slower than most MusiXTeX - preprocessors) - -CONFIGURING and COMPILING - to install GNU LilyPond, simply type: - - configure - make - make install - - This will install the following files: - - /usr/local/man/man1/mi2mu.1 - /usr/local/man/man1/convert-mudela.1 - /usr/local/man/man1/mudela-book.1 - /usr/local/man/man1/lilypond.1 - /usr/local/lib/libflower.{so,a} - /usr/local/bin/lilypond - /usr/local/bin/mi2mu - /usr/local/share/lilypond/* - /usr/lib/texmf/texmf/tex/lilypond/* - - The TeX include directory is detected dynamically, but it - can be adjusted with --enable-tex-prefix and --enable-tex- - dir. 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: - - export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR" - configure - - 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: - - - - -7/May/98 LilyPond 0.1.63 2 - - - - - -INSTALL(1) LilyPond documentation INSTALL(1) - - - configure --prefix=/usr/local --enable-tex-prefix=/usr/lib/texmf - - Since GNU LilyPond currently is beta, you are advised to - also use - - --enable-debugging - --enable-checking - - other options include: - - --enable-shared - Make a shared library (gnu/linux, solaris (?) only ) - - --enable-printing - Enable debugging print routines (lilypond -d option) - - --enable-optimise - Set maximum optimisation: compile with -O2 - - --enable-profiling - Compile with support for profiling - - --enable-tex-prefix - Set the directory where TeX and Metafont live - - --enable-tex-dir - Set then directory TeX input is in (detected as a - subdir of tex-prefix). This should be a directory - that is reachable both for tex and latex. On my - system the best choice would be - /usr/lib/texmf/texmf/tex/generic//. - - --enable-mf-dir - Set the directory mf input is in (idem). On my - system the best choice would be - /usr/lib/texmf/texmf/fonts/source/public/. - - --enable-config - 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). - - - - -7/May/98 LilyPond 0.1.63 3 - - - - - -INSTALL(1) LilyPond documentation INSTALL(1) - - -CONFIGURING FOR MULTIPLE PLATFORMS - If you want to compile LilyPond with different - configuration settings, then, you can use the --enable- - config option. Example: suppose I want to build with and - without profiling. Then I'd use the following for the - normal build, - - configure --prefix=~ --disable-optimise --enable-checking - make - make install - - and for the profiling version, I specify a different - configuration. - - configure --prefix=~ --enable-profiling --enable-config=optprof --enable-optimise --disable-checking - make configuration=optprof - make configuration=optprof install - - -INSTALLING - If you have done a successful make, then a simple - - make install - - 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. - -CAVEATS - o The -O2 option to gcc triggers a gcc bug on DEC Alpha - in dstream.cc. You should turn off this flag for this - file. - - o Perl5.003 and Perl5.004 use different syntax for - pod2html. - -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: - - - - - - - - - - - -7/May/98 LilyPond 0.1.63 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..> - init//performer.ly]]][input/kortjakje.ly] - Creating elements ...[8][16][24][25] - Preprocessing elements... - Calculating column positions ... [14][25] - Postprocessing elements... - TeX output to someinput.tex ... - Creating MIDI elements ...MIDI output to someinput.midi ... - - hw:~/musix/spacer$ xdvi someinput& - [1] 855 - - Check out the input files, some of them have comments - Please refer to the man page for more information. - -REDHAT LINUX - RedHat Linux users can compile an RPM. A spec file is in - make/out/lilypond.spec. You should install a gif file - called lelie_icon.gif along with the sources. You can - generate this gif file by typing - - make gifs - - in the directory Documentation. - -DEBIAN GNU/LINUX - A Debian package is also available; contact Anthony Fok - . The build scripts are in the - subdirectory debian/ - -WINDOWS NT/95 - So, you're stuck with Windows, eh? Well, don't worry, you - just need (to get) Cygnus' windows32 port of gnu - development stuff; have a look at - http://www.cygnus.com/gnu-win32. - - To make GNU LilyPond under, brr, aargh, shudder... - windows32, well, simply type: - - bash configure - make - - Note If you rely on broken DOS/Windows tools such as - pkzip/WinZIP to unpack the distribution, make sure the - entire source tree is unpacked correctly, in particular - the empty out directories (flower/out, lib/out et. al.) - -AUTHORS - Han-Wen Nienhuys - - Jan Nieuwenhuizen - - - - -7/May/98 LilyPond 0.1.63 5 - - - - - -INSTALL(1) LilyPond documentation INSTALL(1) - - - Have fun! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -7/May/98 LilyPond 0.1.63 6 - -