I'm having trouble invoking the eps backend in the first place.
2.9.16 under OS X Intel with this helper script to call lily.
%%% HELPER SCRIPT %%%
#! /bin/sh
export LILYPOND_DESTDIR=`pwd`
export
GS_LIB="/Applications/LilyPond.app/Contents/Resources/share/ghostscript/8.50/lib"
date
python "/Applications/LilyPond.app/Contents/Resources/lilycall.py"
"/Applications/LilyPond.app/" "--backend=eps" $1
echo 'debug'
%%% END HELPER SCRIPT %%%
Here's the test file.
%%% TEST FILE%%%
\version "2.9.16"
\new Staff {
c'4
}
%%% END TEST FILE %%%
And here's the result of running the helper script against the test file.
%%% OUTPUT %%%
Sun Aug 27 23:44:35 CDT 2006
GNU LilyPond 2.9.16
Processing `300.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Calculating line breaks... [2]
Drawing systems...
Calculating page breaks...
Writing 300-systems.tex...
Writing 300-systems.texi...
Layout output to `300-1.eps'...
Converting to `300-1.pdf'...
`gs -q -dSAFER -dEPSCrop -dCompatibilityLevel=1.4 -dNOPAUSE
-dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="300-1.pdf" -c
.setpdfwrite -f "300-1.eps"' failed (256)
error: failed files: "300.ly"
debug
%%% END OUTPUT %%%
I'm missing something obvious since nobody else is having trouble
invoking the eps backend in the first place ... any clues? (I haven't
yet worked in the -dno-gs-font-load option because I'm wanting to get
the eps stuff working first ...)
--
Trevor Bača
address@hidden
... like the dew, or like lightning ...