HACKING

   1 * How to run lilypond from the development tree?
   2
   3 If you want to contribute and can build LilyPond yourself, there's no
   4 need to install that development version; you can run it from the
   5 build tree.
   6
   7 Use the scripts below to configure and select to use the
   8 lilypond from the local build tree like this:
   9
  10   $ clily && make
  11   $ . here-lily
  12
  13
  14 clily:
  15 #!/bin/bash
  16
  17 [ -x configure ] || ./autogen.sh --noconf
  18 rm -f config.cache
  19 ./configure --prefix=$(pwd) --infodir=$(pwd)/share/info --disable-optimising --enable-gui "$@"
  20
  21 here-lily:
  22 # source me
  23
  24 export PATH=$(pwd)/lily/out:$(pwd)/scripts/out:$PATH
  25
  26 unset LILYPONDPREFIX
  27 unset TEXMF
  28
  29 # ugh: must fool-proof other TeX environment variables
  30 TEXINPUTS=:
  31 MFINPUTS=:
  32 TFMFONTS=:
  33
  34 . VERSION
  35 FULL_VERSION=$MAJOR_VERSION.$MINOR_VERSION.$PATCH_LEVEL
  36 if [ -n "$MY_PATCH_LEVEL" ]; then
  37    FULL_VERSION=$FULL_VERSION.$MY_PATCH_LEVEL
  38 fi
  39
  40 datadir=$(pwd)/share/lilypond/$FULL_VERSION
  41 export TEXMF="{$datadir,"`kpsexpand  \\$TEXMF`"}"
  42
  43 export GS_FONTPATH="$datadir/fonts/type1:/usr/share/texmf/fonts/type1/bluesky/cm:/usr/share/texmf/fonts/type1/public/ec-fonts-mftraced"
  44 export GS_LIB="$datadir/ps:$GS_FONTPATH"
  45