The 5th Jan zip file for mingw runs but the LilyPond does not give a typeset. Stranger still the checking for grace note problems script behaves differently - it is one of the things that I fixed yesterday. Given an identical file it misbehaves on the zip version but is ok on my Debian build.
Richard On Mon, 2016-01-04 at 22:31 -0600, Jeremiah Benham wrote: > I decided to take a darwin binary from the last build. I took the the > original darwin LilyPon 2.18.2 and copied it over something like this: > cp ../../LilyPond.app/Contents/Resources/bin/lilypond Resources/bin/ > cp ../../LilyPond.app/Contents/Resources/lib/libgmp.dylib > Resources/lib > cp ../../LilyPond.app/Contents/Resources/lib/libgmp.3.dylib > Resources/lib > cp ../../LilyPond.app/Contents/Resources/shar Resources/lib > > cp ../../LilyPond.app/Contents/Resources/share/lilypond/current/scm/* > ./Resources/share/lilypond/current/scm/ > > cp ../../LilyPond.app/Contents/Resources/share/lilypond/current/ > ./Resources/share/lilypond/current/scm/ > > > > The less I have to compile the better. If I can only find a way to not > have to rebuild all the dependent libs, it would less time and > resources to compile only denemo. It could be rebuilt on every git > commit. I think a script might do it. > > > Jeremiah > > > On Mon, Jan 4, 2016 at 4:10 PM, Richard Shann > <[email protected]> wrote: > On Mon, 2016-01-04 at 15:17 -0600, Jeremiah Benham wrote: > > Lilypond 2.18.2 appears to be working for the linux binary. > It does > > not compile > > for darwin. It says somehting like ssize_t is not defined > in this > > scope. > > > > > > http://denemo.org/~jjbenham/gub/target/darwin-x86/log/lilypondcairo.log > > that's some sort of mixup with the set of headers being used, > presumably. The warning just before the ssize_t error, about > HUGE_VAL > being too large, might hint that it is a 32/64 bit issue > > > > If I simply copy the binaries over from the official mingw > lilypond, > > will it work? > > did you mean "official darwin lilypond"? > > there would be some way of merging a lilypond build and a > denemo one > rather than building both, though I've never been clear > whether the two > have been sharing the same Scheme headers/libraries etc ... > LilyPond is > guile 1.8 while I think usually denemo is using 2.0 > > Do you have a working mingw with 2.18.2 LilyPond? > > Richard > > > > > > > > Jeremiah > > > > On Mon, Jan 4, 2016 at 5:27 AM, Richard Shann > > <[email protected]> wrote: > > On Sun, 2016-01-03 at 17:44 +0000, Richard Shann > wrote: > > > On Sun, 2016-01-03 at 09:09 -0600, Jeremiah Benham > wrote: > > > > The server is back up. I just compiled a mingw > binary for > > testing > > > > > > I've tested the zip version of this (dated 3rd > Jan). The > > playback view > > > has a bug to do with .mid instead of .midi on > windows. I've > > fixed this, > > > but more seriously it fails to generate good SVG > on one of > > the files > > > tested - this is because of the unstable version > of LilyPond > > shipped > > > with this binary - I pointed Denemo to a > separately > > installed 2.18 > > > LilyPond and it typeset fine. > > > I think you have an idea how to ship with the > stable > > LilyPond? > > > > > > I've tested the 4th Jan zip file, it comes with > LilyPond > > 2.18.2 but this > > LilyPond crashes (Visual C++ throws up a window but > the window > > is > > blank). Using the external version of 2.18.2 then > everything > > runs ok. > > > > Richard > > > > > > > > > > > > > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
