> Just thought I'd let you know... > > lilypond-1.5.55 builds succesfully on CygWin with two only two workarounds > required, neither of which I am competent to fix myself.
Great news anyway! > 3. The resultant configuration doesn't include linkages for python (used by > python/midi.lo). To work around this problem, open config.make and edit the > USR_LDFLAGS to read > > USER_LDFLAGS = -L/usr/lib -lguile > /bin/cygwin1.dll -lm -L/usr/lib/python2.2/config/ -lpython2.2.dll That's simple to solve, just read the FAQ at the bottom of http://lilypond.org/wiki/?LilyPondInstall > 4. Run > $ make all 2>&1 | tee log.make > > This fails somewhere in documentation tree build scripts, but will > successfully build everything needed to run lily. That's a problem with Python 2.2, it's the same on UNIX. > 5. The install make procedure can't deal with .exe files. Cygwin does > bizarre things with them. lilypond-1.5.55/stepmake/bin/install-sh fails when > trying to chmod a temporary file of the form #input.nnnn#.exe (presumably > because the shell is smart enough to ignore .exe extensions, but chmod is > not. To work around this problem, temporarily rename lily/out/lilypond.exe > to just plain lily/out/lilypond (we'll rename it back again in step 7). This could probably be solved fairly easily in the make files. /Mats _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
