INSTALL(1) LilyPond documentation INSTALL(1) NNNNAAAAMMMMEEEE INSTALL - installing GNU LilyPond DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN This page documents installation and compilation of GNU LilyPond AAAABBBBSSSSTTTTRRRRAAAACCCCTTTT You do something which looks remotely like configure make make install tar -C /usr/lib/texmf/fonts/source/ -zxf musixtex-T73.tgz 'mf/*' The detailed instructions follow here. PPPPRRRREEEERRRREEEEQQQQUUUUIIIISSSSIIIITTTTEEEESSSS For compilation you need. +o A Unix system with GNU tools. GNU LilyPond is known to run on these unices: 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 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) RRRRUUUUNNNNNNNNIIIINNNNGGGG GNU LilyPond does use a lot of resources. For operation you need the following: +o TeX +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 ftp://ftp.shsu.edu/tex-archive/macros/musixtex/taupin 8/Aug/97 LilyPond 0.1.11 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 _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 scripts are written in Perl. Most documentation was created with the perl's Plain Old Documentation. (I use 5.003) +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----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 your taste: 8/Aug/97 LilyPond 0.1.11 2 INSTALL(1) LilyPond documentation INSTALL(1) 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 --------hhhheeeellllpppp. 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 _/_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: 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 ----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) [obsolete] 8/Aug/97 LilyPond 0.1.11 3 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 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 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 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 8/Aug/97 LilyPond 0.1.11 4 INSTALL(1) LilyPond documentation INSTALL(1) 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& 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_/_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) 8/Aug/97 LilyPond 0.1.11 5 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 AAAAUUUUTTTTHHHHOOOORRRRSSSS Han-Wen Nienhuys Jan Nieuwenhuizen Have fun! 8/Aug/97 LilyPond 0.1.11 6