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     lily/out/lilypond input/simple.ly
  12
  13 or
  14
  15     ./configure && make
  16     LILYPONDPREFIX=$(pwd)/out out/lily/lilypond input/simple.ly
  17
  18
  19 clily:
  20 #!/bin/bash
  21
  22 [ -x configure ] || ./autogen.sh --noconf
  23 rm -f config.cache
  24 ./configure --prefix=$(pwd)/out --infodir=$(pwd)/share/info --disable-optimising --enable-gui "$@"
  25
  26 here-lily:
  27 # source me - switching to older versions of LilyPond
  28
  29 export PATH=$(pwd)/lily/out:$(pwd)/scripts/out:$PATH
  30
  31 unset LILYPONDPREFIX
  32 unset TEXMF
  33
  34 # ugh: must fool-proof other TeX environment variables
  35 TEXINPUTS=:
  36 MFINPUTS=:
  37 TFMFONTS=:
  38
  39 . VERSION
  40 FULL_VERSION=$MAJOR_VERSION.$MINOR_VERSION.$PATCH_LEVEL
  41 if [ -n "$MY_PATCH_LEVEL" ]; then
  42    FULL_VERSION=$FULL_VERSION.$MY_PATCH_LEVEL
  43 fi
  44
  45 datadir=$(pwd)/share/lilypond/$FULL_VERSION
  46 export TEXMF="{$datadir,"`kpsexpand  \\$TEXMF`"}"
  47
  48 export GS_FONTPATH="$datadir/fonts/type1:/usr/share/texmf/fonts/type1/bluesky/cm:/usr/share/texmf/fonts/type1/public/ec-fonts-mftraced"
  49 export GS_LIB="$datadir/ps:$GS_FONTPATH"
  50