Re: problem with lilypond from the command line

[Graham Percival]

Han-Wen,

It seems that the LILYPOND_DATADIR update in 2.11 was accidentally 
merged with the stable branch.  Could we update lilycall.py in 2.10 to 
use the same shell variable (not LILYPONDPREFIX) ?

Cheers,
- Graham

Jacob Rundall wrote:
> Hi Graham,
>
> Thanks for getting back to me.  I think the script might have shipped 
> with Lilypond in the past, but it doesn't any more even if that was 
> the case.  But it seems to me that the shell script I'm using isn't 
> really the problem, so let me take it out of the picture.  When I run 
> the lilycall.py script on its own:
>
> cd /Applications/Lilypond.app/Contents/Resources
> python lilycall.py /Applications/Lilypond.app
>
> I get the same error:
>
> GNU LilyPond 2.10.29
> error: LILYPONDPREFIX is obsolete, use LILYPOND_DATADIR
>
> Like I mentioned, if I simply change that variable name within the 
> lilycall.py script, all is well.  I don't get any errors in the GUI - 
> thanks very much for that!!  But since the fix is, or at least seems 
> to be, so straightforward, it might be worth fixing it.
>
> Thanks again,
>
> Jake
> On Sep 5, 2007, at 4:31 AM, Graham Percival wrote:
>
> > Give the filename, I presume that you're using OSX?
> >
> > Where did the script in /usr/local/bin come from?  I don't think that 
> > we install such a script (although I could be wrong)   We recently 
> > changed the variable name; see the NEWS file for 2.11.  Perhaps this 
> > update was accidentally merged back into 2.10... or perhaps your 
> > script was designed for a different version of LilyPond?
> >
> > Do you get any errors when you run from the GUI?  We'll be making a 
> > new stable release soon, so if it only affects command-line users, 
> > I'd rather concentrate on bugs in the upcoming release.  :)
> >
> > Cheers,
> > - Graham
> >
> >
> > Jake Rundall wrote:
> > > The script (lilypond) listed at the end of this message is in 
> > > /usr/local/bin.
> > > When I execute it, I get the following error:
> > >
> > > GNU LilyPond 2.10.29
> > > error: LILYPONDPREFIX is obsolete, use LILYPOND_DATADIR
> > >
> > > If I edit Lilypond.app/Contents/Resources/lilycall.py by changing
> > > 'LILYPONDPREFIX' to 'LILYPOND_DATADIR'
> > > everything seems to work fine.
> > >
> > >
> > >
> > >
> > > #!/bin/sh
> > >
> > > #
> > > # Example file for invoking LilyPond.app from the commandline. #
> > >
> > > # customize the following variables
> > >
> > > ## where was the app installed?
> > > INSTALLDIR=/Applications
> > >
> > > ## uncomment to get some debugging info, and leave .ps files
> > > # export LILYPOND_WRAPPER_DEBUG=1
> > >
> > > if [ "$1" == "--print-appdir" ]; then
> > >   echo "$INSTALLDIR/LilyPond.app/"
> > >   exit 0
> > > fi
> > >
> > >
> > > # where to put the output
> > > export LILYPOND_DESTDIR=`pwd`
> > >
> > > # run the program
> > > python "$INSTALLDIR/LilyPond.app/Contents/Resources/lilycall.py" \
> > >   "$INSTALLDIR/LilyPond.app/" $*
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > bug-lilypond mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/bug-lilypond