On Tue, Feb 16, 2021 at 2:34 PM Richard Shann <[email protected]> wrote: > > On Tue, 2021-02-16 at 11:04 -0600, Jeremiah Benham wrote: > > I am going to look into it. I like to make sure it work in wine > > first. Last time we had this problem lilypond had trouble finding one > > of those files that guile needed to run. > I've run lilypond-windows.exe on its own on windows Vista with a simple > input file and it created an empty temporary file (obscure name) but > gave no other output not even to the terminal.
In wine it complained about not having permission. I recursively chmod 777 the working directory but that did not help. > > How long has the nightly build been broken? > I don't know - anyone with their own LilyPond installation (and the > preferences set to find it) wouldn't notice... > > I remember Richards mingw build working. > ??? mxe build? I have been building just denemo and copying onto a > structure containing a LilyPond mxe build from some time back. Do you lilypond building with mxe. I am going to look into doing that myself because that will solve all our problems here. I have been copying over the official lilypond that they build using gub using this command: rsync -a --ignore-existing LilyPond/usr/ denemo/ I did this because simply copying it over breaks denemo. I could put it in another directory but then the file is too large and there would be a bunch of duplicate files. I am going to look into building lilypond using MXE. Since I am at it, should we be packaging the latest stable (2.22) or version 2.20? Jeremiah >This is > the first time in ages that I've refreshed that build from the > overnight zip file. When I try to run lilypond-window.exe --version > from a terminal on Vista I see no output, but I think that may be just > because it is a "no-console" build. > > Richard >
