Re: [Denemo-devel] Release 0.8.16 - Gub Status

[Richard Shann]

I have built using the my old gub, and Nils' findings apply to this
also: the .pdf file is created with zero length, but lilypond does not
start until denemo exits, whereon the .pdf file is populated.
So this is *not* a bug caused by Nils' new gub code.
It seems the bug is because the code which generates a new name for each
print during a denemo session has been disabled. I'll look into it.
Richard

On Tue, 2010-03-23 at 21:54 +0000, Richard Shann wrote:
> OK I have set all these up and checked the code into git.
> One incomplete feature is that the  GUILE_LOAD_PATH is over-written, as
> we have to be sure that the denemo scm files are in it. But this would
> mean that we would get the newer lilypond scm files if someone had
> already set GUILE_LOAD_PATH to an older installation of lilypond and
> wished to use it.
> LilyPond failing to run until Denemo exits would make sense if Denemo
> still had the .ly file open, as windows does file locking (I think). But
> why this should show now I can't imagine.
> A useful test would be to install LilyPond system wide as well as inside
> Denemo and see if the same holds.
> Richard
> 
> 
> On Tue, 2010-03-23 at 21:40 +0100, Nils Gey wrote:
> > > Actually the push failed, and I will delay while further investigations
> > > take place
> > > Richard
> > 
> > Investigation Complete:
> > 
> > I finally got all lilypond enviroment variables right to run lilypond 
> > standalone and produce a valid pdf file. 
> > We need to copy this in Denemo.
> > 
> > GUILE_LOAD_PATH: 
> > ...\denemo\usr\share\guile
> > ...\denemo\usr\share\guile\1.8
> > ...\denemo\usr\share\lilypond\current\scm //if we build lilypond git, its 
> > "current"
> > ...\denemo\usr\share\guile
> > ...\denemo\usr\share\guile
> > 
> > PATH:
> > ...\denemo\usr\bin
> > ...\denemo\usr\lib
> > 
> > LILYPOND_DATA_PATH 
> > ...\denemo\usr\share\lilypond\current\
> > 
> > LILYPOND_VERBOSE
> > 1
> > 
> > this last one is actually not needed, but may be nice for future testing.
> > 
> > 
> > Problems remain, two are just to inform you, the third is the real one:
> > 
> > 1)PDFs show up from where path\to\lilypond.exe was invoked. Means: The 
> > current working dir.
> > 
> > 2)Running lilypond from the command line has problems. Maybe backslash\
> > escaping problems. 
> > janneke: "and no-one uses the command line, apparently ;-)"
> > 
> > If you place the .ly file to the dir in %PATH% it works. And it works, if 
> > you do it with a file association, that means the console it the reason 
> > that it does not work (thats why I think its some escaping problem)
> > 
> > 
> > BUT (good news) from within Denemo these last two problems are no problems. 
> > The file gets generated and ends in the right place. 
> > 
> > 3)However the ly/pdf file does not gets processed until Denemo is closed. 
> > Don't ask me, I don't know why...
> > You see the lilypond terminal open all the time, but nothing happens, and 
> > if you quit Denemo the processing begins and the pdf is right there.
> > 
> > Nils
> 
> 
> 
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel