Pedro Kroger writes:
> ok, I'm going to do the same. Could you, please, refresh my memory and
> tell how to do that? :-) (I remember you posted something about it some
> time ago but I can't find it on the archive).
Here's what I'm using.
RUNNING LilyPond from build directory
CONFIGURE like this
################
# ~/bin/clily
[ -x configure ] || ./autogen.sh --noconfig
./configure --prefix=$(pwd) --infodir=$(pwd)/share/info --disable-optimising
--enable-gui "$@"
################
MAKE all
For running muliple build trees, source the here-lily script:
################
# ~/bin/here-lily
export PATH=$(pwd)/lily/out:$(pwd)/scripts/out:$PATH
unset LILYPONDPREFIX
# fool-proof tex vars
TEXINPUTS=:
MFINPUTS=:
TFMFONTS=:
unset TEXMF
datadir=$(pwd)/share/lilypond
export TEXMF="{$datadir,"`kpsexpand \\$TEXMF`"}"
################
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
