X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;ds=sidebyside;f=INSTALL.text;h=012ed4cf709afe304ab760045cfea3a36a824d01;hb=946c135a338e2daadfed8da3026f0ed9d29bf9ad;hp=66e6a45bce7bf9b4a8542ce0d08e47b381e3f6c8;hpb=a41a7fb966e8552cc8da7c4eab1b60eb7b8eff3a;p=lilypond.git diff --git a/INSTALL.text b/INSTALL.text index 66e6a45bce..012ed4cf70 100644 --- a/INSTALL.text +++ b/INSTALL.text @@ -5,63 +5,63 @@ INSTALL(1) LilyPond documentation INSTALL(1) NNNNAAAAMMMMEEEE - INSTALL - installing LilyPond + INSTALL - installing GNU LilyPond DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN - This page documents installation and compilation of + This page documents installation and compilation of GNU LilyPond -IIIIMMMMPPPPOOOORRRRTTTTAAAANNNNTTTT - if you have downloaded a +AAAABBBBSSSSTTTTRRRRAAAACCCCTTTT + You do something which looks remotely like - *.pre* + configure + make + make install + tar -C /usr/lib/texmf/fonts/source/ -zxf musixtex-T73.tgz 'mf/*' + + The detailed instructions follow here. - version, then this is version is _n_o_t meant for producing - nice output, but to keep your patchsets up to date. It - might not even compile. PPPPRRRREEEERRRREEEEQQQQUUUUIIIISSSSIIIITTTTEEEESSSS For compilation you need. - +o Unix. LilyPond is known to run on Linux, AIX, Digital - Unix and Solaris - If you have the Cygnus WIN32 port of the GNU utils, - it will even work in Lose NT/95, but don't promise to - support it. + +o A GNU system: GNU LilyPond is known to run on these + GNU systems: Linux, AIX, Digital Unix and Solaris. - +o GNU C++ v2.7 or better, with libg++ installed. Version - 2.7.2 or better recommended. I almost positive that - it will not compile with AT&T CC. + 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 Bash. Most scripts will continue to work with a stock - sh, but they might generate (harmless) syntax errors + +o GNU C++ v2.7 or better, with libg++ installed. + Version 2.7.2 or better recommended. - +o GNU make. + +o GNU make. - +o Flex (2.5.1 or better). + +o Flex (2.5.1 or better). - +o Bison. + +o Bison. (Version 1.25 or better) -RRRREEEECCCCOOOOMMMMMMMMEEEENNNNDDDDEEEEDDDD - +o Perl. Some (mostly unimportant scripts) use Perl for - trivial operations. The documentation was created - with the perl's Plain Old Documentation. +RRRRUUUUNNNNNNNNIIIINNNNGGGG + GNU LilyPond does use a lot of resources. For operation + you need the following: - +o (GNU) find + +o TeX -CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRIIIINNNNGGGG aaaannnndddd CCCCOOOOMMMMPPPPIIIILLLLIIIINNNNGGGG - to install LilyPond, simply type: + +o The MusixTeX fonts (I included 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 site, e.g. at - configure - make install - - This will install the following files: + ftp://ftp.shsu.edu/tex-archive/macros/musixtex/taupin + ftp://ftp.tex.ac.uk/tex-archive/macros/musixtex/taupin -25/Mar/97 LilyPond 0.0.45 1 +24/Dec/97 LilyPond 0.1.38 1 @@ -70,17 +70,73 @@ CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRIIIINNNNGGGG a INSTALL(1) LilyPond documentation INSTALL(1) + ftp://ftp.dante.de/tex-archive/macros/musixtex/taupin + + You only need the contents of the _m_f_/ + subdirectory of the package. The primary site of + the Taupin version is ftp://hprib.lps.u- + psud.fr/pub/music_zips/musixtex.zip + + Andreas Egler's version of MusixTeX, now called + OpusTeX, will also work. Andreas moved some + characters around in the fonts, so you have to + edit the definitions in tex/eglerdefs.tex (patch + appreciated) + +RRRREEEECCCCOOOOMMMMMMMMEEEENNNNDDDDEEEEDDDD + Although not strictly necessary, these are recommended to + have. + + +o Perl-5. Most documentation was created with the + perl's Plain Old Documentation. (I use 5.003) + + +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 + --------eeeennnnaaaabbbblllleeee----cccchhhheeeecccckkkkiiiinnnngggg compile. It's lot slower than + most MusiXTeX preprocessors) + +CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRIIIINNNNGGGG aaaannnndddd CCCCOOOOMMMMPPPPIIIILLLLIIIINNNNGGGG + to install GNU LilyPond, simply type: + + configure + 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 --------eeeennnnaaaabbbblllleeee----tttteeeexxxxpppprrrreeeeffffiiiixxxx. 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: + can be adjusted with --------eeeennnnaaaabbbblllleeee----tttteeeexxxx----pppprrrreeeeffffiiiixxxx and --------eeeennnnaaaabbbblllleeee----tttteeeexxxx---- + ddddiiiirrrr. 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 + + + +24/Dec/97 LilyPond 0.1.38 2 + + + + + +INSTALL(1) LilyPond documentation INSTALL(1) + + + your taste: export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR" configure @@ -93,41 +149,117 @@ INSTALL(1) LilyPond documentation INSTALL(1) configure --prefix=/home/me_myself_and_I/ - Since LilyPond currently is beta, You are advised to also - use + In this case, you will have to set MFINPUTS, and TEXINPUTS + accordingly. + + If you want to install GNU LilyPond in _/_u_s_r_/_l_o_c_a_l, and + your TeX has no default hooks for local stuff (mine is + broken too), you can do: - --enable-debug + 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-printing - --enable-optimise - --enable-profiling + --enable-shared + Make a shared library (gnu/linux, solaris (?) + only ) + + --enable-printing + Enable debugging print routines (lilypond ----dddd + option) + + --enable-optimise + Set maximum optimisation: compile with ----OOOO2222 + + --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) + + --enable-mf-dir + Set the directory mf input is in (idem) + + + + +24/Dec/97 LilyPond 0.1.38 3 - The option --------eeeennnnaaaabbbblllleeee----ooooppppttttiiiimmmmiiiisssseeee is recommended for Real Life - usage. - If you do + + +INSTALL(1) LilyPond documentation INSTALL(1) + + + --enable-out-dir + Set the directory for machine generated output. + + All options are documented in the _c_o_n_f_i_g_u_r_e help + The option --------eeeennnnaaaabbbblllleeee----ooooppppttttiiiimmmmiiiisssseeee 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 _o_u_t_/ (which contain all + files generated during compilation). + + BBBBuuuuiiiillllddddiiiinnnngggg ffffoooorrrr mmmmuuuullllttttiiiipppplllleeee hhhhoooossssttttssss + + LilyPond does not follow the GNU standards when it comes + to configuring and making Makefiles. In LilyPond, _m_a_k_e + generates _a_l_l output in output directories (called _o_u_t_/, + by default). You can have multiple compiles from the same + source-tree, by overriding the setting for the output + directory. + + 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 - everything will be compiled, but nothing will be - installed. The resulting binaries can be found in the - subdirectory _b_i_n_/. + and I want to do profiling. For that I use -RRRRUUUUNNNNNNNNIIIINNNNGGGG - LilyPond does use a lot of resources. For operation you - need the following: + configure --prefix=~ --enable-debugging --disable-printing\ + --disable-checking --enable-profiling --enable-optimise\ + --enable-out-dir=out-profile + + 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. + +IIIINNNNSSSSTTTTAAAALLLLLLLLIIIINNNNGGGG + If you have done a successful make, then a simple + + make install - +o A fast computer (a full page of music typically takes 1 - minute on my 486/66, using the --------eeeennnnaaaabbbblllleeee----cccchhhheeeecccckkkkiiiinnnngggg - compile. It's lot slower than most MusiXTeX - preprocessors) + should do the trick. + Install the musixtex fonts in a directory which TeX and MF + knows (if you are root, look for a directory which -25/Mar/97 LilyPond 0.0.45 2 + +24/Dec/97 LilyPond 0.1.38 4 @@ -136,42 +268,96 @@ RRRRUUUUNNNNNNNNIIIINNNNGGGG INSTALL(1) LilyPond documentation INSTALL(1) - +o TeX + contains the directories with AMS and CM source (*.mf) + files. Create a subdir lilypond or musixtex and copy the + fonts into that). Do not forget to rehash TeX (if + applicable) + + Example: my fonts are in + _/_u_s_r_/_l_o_c_a_l_/_l_i_b_/_t_e_x_f_o_n_t_s_/_m_u_s_i_x_t_e_x_/, and I have a symlink + pointing to that in + _/_u_s_r_/_l_i_b_/_t_e_x_m_f_/_t_e_x_m_f_/_f_o_n_t_s_/_s_o_u_r_c_e_/_p_u_b_l_i_c_/. After I copied + the files, I ran "texhash" + +CCCCAAAAVVVVEEEEAAAATTTTSSSS + +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: + +EEEEXXXXAAAAMMMMPPPPLLLLEEEE + This is what I type in my xterm: + + lilypond someinput.ly + tex lelie.tex + xdvi test& - +o The MusixTeX fonts. (I use those found in MusixTeX T.59) + 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// + <..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 lelie.tex ... + Creating MIDI elements ...MIDI output to lelie.midi ... + + hw:~/musix/spacer$ xdvi lelie& + [1] 855 + + Check out the input files, some of them have comments Please refer to the man page for more information. RRRREEEEDDDDHHHHAAAATTTT LLLLIIIINNNNUUUUXXXX RedHat Linux users should be able to get a RPM. A spec - file is in _m_a_k_e_/_l_i_l_y_p_o_n_d_._s_p_e_c. + file is in _m_a_k_e_/_o_u_t_/_l_i_l_y_p_o_n_d_._s_p_e_c. You should be able to + create an rpm as a normal user. Be sure you have a + ~/.rpmrc, and edit the RPM-dir in _V_a_r_i_a_b_l_e_s_._m_a_k_e. (If you + create the RPM as a normal user the permissions will not + be set correctly, unfortunately) -WWWWIIIINNNNDDDDOOOOZZZZEEEE - Windows NT: - you need the cygnus win32 gnu port development stuff; have - a look at http://www.cygnus.com/gnu-win32. - to make LilyPond under, brr, aargh, well, simply type: - bash configure - make win32 + +24/Dec/97 LilyPond 0.1.38 5 -PPPPLLLLAAAATTTTFFFFOOOORRRRMMMMSSSS - LilyPond (pl 0.0.39) is known to compile on the following - platforms: - * linux 2.0.28, g++ 2.7.2[.1] - * aix 4.1, g++ 2.7.2 - * windows-nt 4.0, cygnus gnu-win32 beta17.1 (~=g++ 2.7.2) - * linux 2.0.28 X to doze, gcc-go32 (~=g++ 2.7.2) [exec. untested] +INSTALL(1) LilyPond documentation INSTALL(1) + + +DDDDEEEEBBBBIIIIAAAANNNN GGGGNNNNUUUU////LLLLIIIINNNNUUUUXXXX + A Debian package is in the works + +WWWWIIIINNNNDDDDOOOOWWWWSSSS NNNNTTTT////99995555 + 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 + + NNNNooootttteeee If you rely on broken DOS/Windows tools such as + pkzip/WinZIP to unpack the distribution, make sure the + eeeennnnttttiiiirrrreeee source tree is unpacked correctly, in particular + the empty out directories (_f_l_o_w_e_r_/_o_u_t, _l_i_b_/_o_u_t et. al.) + AAAAUUUUTTTTHHHHOOOORRRRSSSS - Han-Wen Nienhuys + Han-Wen Nienhuys - Jan Nieuwenhuizen + Jan Nieuwenhuizen Have fun! @@ -193,6 +379,18 @@ AAAAUUUUTTTTHHHHOOOORRRRSSSS -25/Mar/97 LilyPond 0.0.45 3 + + + + + + + + + + + + +24/Dec/97 LilyPond 0.1.38 6