


INSTALL(1)            LilyPond documentation           INSTALL(1)


NNNNAAAAMMMMEEEE
       INSTALL - installing GNU LilyPond

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
       This page documents installation  and compilation of GNU
       LilyPond

IIIIMMMMPPPPOOOORRRRTTTTAAAANNNNTTTT
       if you have downloaded a

               *.pre*

       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    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 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)

RRRREEEECCCCOOOOMMMMMMMMEEEENNNNDDDDEEEEDDDD
       +o    Perl.  Most scripts are written in Perl. The
            documentation was created with the perl's Plain Old
            Documentation.

       +o    (GNU) find

CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRIIIINNNNGGGG aaaannnndddd CCCCOOOOMMMMPPPPIIIILLLLIIIINNNNGGGG
       to install GNU LilyPond, simply type:

               configure
               make install

       This will install the following files:







7/Jul/97                 LilyPond 0.0.74                        1





INSTALL(1)            LilyPond documentation           INSTALL(1)


               /usr/local/man/man1/mi2mu.1
               /usr/local/man/man5/mudela.5
               /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/*
               /usr/lib/texmf/texmf/fonts/source/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:

               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 TEINPUTS
       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




7/Jul/97                 LilyPond 0.0.74                        2





INSTALL(1)            LilyPond documentation           INSTALL(1)


       --enable-profiling
           Compile with support for profiling

       --enable-tex-prefix
           Set the directory where texmf lives

       --enable-tex-dir
           Set then directory tex input is in (detected as a
           subdir of tex-prefix)

       --enable-mf-dir
           Set then directory tex input is in (idem)

       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).

IIIINNNNSSSSTTTTAAAALLLLLLLLIIIINNNNGGGG
       If you have done a successful make, then a simple

               make install

       should do the trick.

       [todo. Obsolete; fonts are in distribution now.]

       Install the musixtex fonts in a directory which TeX and MF
       knows (if you are root, look for a directory which
       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_/

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.

RRRRUUUUNNNNNNNNIIIINNNNGGGG
       GNU LilyPond does use a lot of resources. For operation



7/Jul/97                 LilyPond 0.0.74                        3





INSTALL(1)            LilyPond documentation           INSTALL(1)


       you need the following:

       +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)

       +o    TeX

       +o    The MusixTeX fonts (I included those found in
            MusixTeX T.73). Beware, the clef symbol has changed
            position in the Egler version, a.k.a. OpusTeX)

       At this time, GNU LilyPond output looks nice, but is not
       of production quality. If you're not discouraged; 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:

               hw:~/musix/spacer$ lilypond input/kortjakje.ly
               GNU LilyPond 0.0.71 #20/FlowerLib 1.1.20 #0
               Parsing ... [/home/hw/share/lilypond/init//symbol.ini  <..snip..>
               ..      .ini]][input/kortjakje.ly]
               Creating elements ...
               Preprocessing elements...
               Calculating column positions ... [3][8][13][17][21][25]
               Postprocessing elements...
               TeX output to lelie.tex ...

               hw:~/musix/spacer$ tex lelie
               This is TeX, Version 3.14159 (C version 6.1)
               (lelie.tex
               Hyphenation patterns for english, dutch, german, loaded.
               (/home/hw/lib/texmf/tex/lilypond/lilyponddefs.tex) [1] )
               Output written on lelie.dvi (1 page, 8944 bytes).
               Transcript written on lelie.log.

               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. 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





7/Jul/97                 LilyPond 0.0.74                        4





INSTALL(1)            LilyPond documentation           INSTALL(1)


WWWWIIIINNNNDDDDOOOOZZZZEEEE
       Windows NT:

       you need the cygnus windows32 gnu port development stuff;
       have a look at http://www.cygnus.com/gnu-win32.

       to make GNU LilyPond under, brr, aargh, well, simply type:

               bash configure
               make windows32


PPPPLLLLAAAATTTTFFFFOOOORRRRMMMMSSSS
       GNU LilyPond (pl 0.0.39) is known to compile on the
       following platforms:

       Unix:

               * gnu/linux 2.0.x, g++ 2.7.2[.1]
               * aix 4.1, g++ 2.7.2
               * solaris 2.5, g++ 2.7.2

       Other:

               * windows-nt 4.0, cygnus gnu-windows32 beta17.1 (~=g++ 2.7.2)
               * gnu/linux 2.0.28 X to doze, gcc-go32 (~=g++ 2.7.2) [exec. untested]


AAAAUUUUTTTTHHHHOOOORRRRSSSS
       Han-Wen Nienhuys <hanwen@stack.nl>

       Jan Nieuwenhuizen <jan@digicash.com>

       Have fun!























7/Jul/97                 LilyPond 0.0.74                        5


