On Thursday, 23 March 2000, Alain CULOS writes:
> Under bare bones DOS shell, lilypond.exe still tries to access cygwin1.dll
> (missing) and the other one when renamed, sorry to say Jan, but both are stil
+ l
> required.
That's really a step backwards. I'll just link to the new cygwin1.dll again.
> OK, thank you for renaming the exe files to *.exe as required for windows.
> I liked the other directory structure - I know Unix lads think it's crazy but
+ I
> like the idea of having my program where I know : in ...\lilypond-Vxxx rather
> than the usual Unix tree.
Yes, I'll do that too.
> Outstanding :
> python scripts to be renamed *.py
I really don't understand these suffix problems. When I had to use
Cygwin under windows, I remember that I didn't use any .exe .py or
whatnot, just doing
bash
$ echo "echo bar" > /bin/foo
$ chmod 755 /bin/foo
$ /bin/foo
bar
should work fine. Same for scripts that start with '#!/bin/python'.
> still/again that dll issue, sorry to nag you, but will you please tell me why
> you really want it, why not forget about it ?
Uhm, I don't understand, what do you mean, forget about it? Anything
you compile with gcc under cygwin will be using the cygwin*.dll
compatibility layer.
Tonight, I've at last got the mingw cross-development tools working.
But mingw is still too minimalistic for compiling guile; it won't work
any time soon.
Greetings,
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
