''

[lilypond.git] / buildscripts / lilypond-profile.sh

diff --git a/buildscripts/lilypond-profile.sh b/buildscripts/lilypond-profile.sh
index c20fa45672fde52ad3f27ca3ab0822e5734c510a..1e03ea439a024d72d408d3dea040a44b2276d1b7 100644 (file)
--- a/buildscripts/lilypond-profile.sh
+++ b/buildscripts/lilypond-profile.sh
@@ -1,17 +1,37 @@
 #!/bin/sh
 
+# Setup TeX/LaTeX Ghostscript environment for LilyPond.
 
-# set environment for LilyPond.  To be installed in /etc/profile.d/
-GS_LIB="@datadir@/afm"
-GS_FONTPATH="@datadir@/ps"
-LILYINCLUDE="@datadir@/ly"
+# Red Hat-like systems should install this in /etc/profile.d/
 
-# include an empty path component for the system wide includes.
-MFINPUTS="@datadir@/mf:"${MFINPUTS:=":"}
-TEXINPUTS="@datadir@/tex:"${TEXINPUTS:=":"}
+# If run by hand or from you .profile, run as follows
+#   . lilypond-profile
 
-export LILYINCLUDE MFINPUTS TEXINPUTS GS_LIB GS_FONTPATH
+datadir=`echo "@datadir@" | sed 's!//!/!g'`
 
-# echo  $LILYINCLUDE $MFINPUTS $TEXINPUTS $GS_LIB $GS_FONTPATH
+# For direct ps output: ps/lilyponddefs.ps
+GS_LIB="$datadir/ps:"${GS_LIB:=""}
+
+# bit silly. for ly2dvi, overrules compiled-in datadir...
+# Better comment this out.  Compiled-in datadir serves exactly the
+# same purpose, but is more likely to be correct (think multiple
+# versions of lilypond).
+# LILYPONDPREFIX="$datadir"
+
+# Add the installation directory to the teTeX system tree, 
+# see Documentation/misc/fontinstallation
+TEXMF="{$datadir,"`kpsexpand  \\$TEXMF`"}"
+
+# LILYPONDPREFIX="$datadir"
+# export LILYPONDPREFIX
+
+# For direct ps output fonts. Add all available TeX Type1 fonts
+GS_FONTPATH=`kpsewhich -expand-path=\$T1FONTS`:${GS_FONTPATH:=""}
+
+
+
+export GS_LIB GS_FONTPATH TEXMF
+
+