new file HACKING

diff --git a/ChangeLog b/ChangeLog
index 63d6da776c81ed3ad370c7f71a83361597e8de1f..c4ccdbece49ae7782ad95547312df84b2bc539f9 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -6,6 +6,8 @@
 
 2005-02-21  Pedro Kroger  <kroeger@pedrokroeger.net>
 
+       * HACKING: new file.
+
        * input/regression/utf8.ly (portuguese): added a portuguese example
        to show latin1 accents.
 

diff --git a/HACKING b/HACKING
new file mode 100644 (file)
index 0000000..2db7792
--- /dev/null
+++ b/HACKING
@@ -0,0 +1,42 @@
+* How to run lilypond from the development tree? 
+
+If you want to contribute and can build LilyPond yourself, there's no
+need to install that development version; you can run it from the
+build tree.
+
+Use the scripts below to configure and select to use the
+lilypond from the local build tree like this:
+
+  $ clily && make
+  $ . here-lily
+
+
+clily:
+#!/bin/bash
+
+[ -x configure ] || ./autogen.sh --noconf
+rm -f config.cache
+./configure --prefix=$(pwd) --infodir=$(pwd)/share/info --disable-optimising
+--enable-gui "$@"
+
+here-lily:
+# source me
+
+export PATH=$(pwd)/lily/out:$(pwd)/scripts/out:$PATH   
+
+unset LILYPONDPREFIX
+unset TEXMF
+
+# ugh: must fool-proof other TeX environment variables
+TEXINPUTS=:
+MFINPUTS=:
+TFMFONTS=:
+
+datadir=$(pwd)/share/lilypond
+export TEXMF="{$datadir,"`kpsexpand  \\$TEXMF`"}"
+
+export
+GS_FONTPATH="$datadir/fonts/type1:/usr/share/texmf/fonts/type1/bluesky/cm:/usr/share/texmf/fonts/ty
+pe1/public/ec-fonts-mftraced"
+export GS_LIB="$datadir/ps:$GS_FONTPATH"
+