lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error in running Lilypond


From: Father Gordon Gilbert
Subject: Re: Error in running Lilypond
Date: Mon, 14 Feb 2011 07:29:54 -0500

On 14/02/2011, Francisco Vila <address@hidden> wrote:
> 2011/2/14 Father Gordon Gilbert <address@hidden>:
>> Thank you -- so I did which for both, and with the .py nothing comes
>> up, and without, it shows /usr/local/bin.  So how do I get these
>> things working?  On this machine, I'll have quite a bit of upgrading,
>> from 2.5.x I believe.  Compiling works now, but convert-ly-ing doesn't
>> yet, even though I've got /usr/local/bin in the main path now.
>
> I'm glad to see it already works for you. To tell you the truth,
> convert-ly doesn'n work for me in lilypondTool.  The whole concept of
> the configuration is windows-oriented, that is: set a folder name for
> the binaries, then set executable names for commands in that folder.
> In Linux we name commands and they work because they are in the path
> if they are properly installed.
>
> I'd like to summarize the whole set of configs for lilypondtool
> commands, for Linux. Forwarding to Bertalan (its author)
>
>
> --
> Francisco Vila. Badajoz (Spain)
> www.paconet.org , www.csmbadajoz.com
>

Thanks Francisco.  I'm gratified that it now works.  I originally
began using Lilypond on a FreeBSD machine in about 2002 (on version
2.2.2, iirc) and did a great deal of work on hymns and the like around
2004-5 with version 2.5.x.  But in various upgrades, my BSD machine
began not to support the various dependencies (or whatever) and I
found it easier to use my Windoze machine.  But in the presence of my
son the computer genius this past weekend, we first got java working,
then jEdit/LilypondTool, then Lilypond.  With that combination going,
I may now try working on Frescobaldi and see how that is.

Thanks to all for your help.  I love this program!

Blessings,

Gordon+

-- 
Fr. Gordon Gilbert
Penetanguishene, ON



reply via email to

[Prev in Thread] Current Thread [Next in Thread]