summaryrefslogtreecommitdiff
path: root/HACKING
blob: 2db7792cfbc9a8727c9e73b403ac92452798d096 (about) (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
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"