On Tuesday, 14 March 2000, Alain CULOS writes:
> Here is my go at the Windows 1.3.31 version.
Thanks.
> Files :
>
> fetdefs.tex
> headers.tex
> Were not present in the 1.3.31 distribution (have they changed since 1.2.0 ?)
+ .
> So that should help.
Yes, that's a bug, thanks.
> My next problem is that I do not have the appropriate cygwin1.dll ... and it
Wow! That's good news: windows recognises the binary as an executable.
(I built it on a GNU/Linux powerpc box, completely untested).
> Now it would be nice if you offered the cygwin1.dll that you linked against s
+ o
> that we are sure we have the right one. And you will not have to worry about
> being in sync with cygnus.
I did, and put it in the same directory, as cygwin1.dll.zip. See:
http://appel.dyndns.org/lilypond/gnu-windows/cygwin1.dll.zip
Would you try if LilyPond runs, if you use that? (Lily won't be realy
usable without the correct .tex files you reported missing, but I'll
make a fresh release of 1.3.34 or later shortly if this works).
> Anyway, why do you want to link against cygwin.dll, is there any Unix specifi
+ cs
> that make the native windows link unworkable as is ? I'd rather if you could
> link using -mno-cygwin if at all possible. Sorry but I don't really want to g
+ o
Hmm, I didn't know about that flag, I'll have a look. I know there's
the mingw package, which could be the way to go. We link agains guile,
so there indeed are some unix symbols that we need.
> compiling the stuff (1/ I'm not too expert at this stuff 2/ I get very
> frustrated 3/ I want to spend my time at too many other nice things to do lik
+ e
> using lilypond and more) although I am willing to test installation/distribut
+ ion
> (either zip, tgz or exe) packages you may want to test now and then.
Thanks for your efforts.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
