Urs, you wrote Thursday, April 18, 2013 4:07 PM > Does that mean that it is 'lilypond-book' on Linux and > 'lilypond-book.py' on Windows?
I don't have a Linux installation to hand to check, but as lilypond-book is written in Python and is not (I think) cross-compiled in GUB to an executable, all that is distributed in the binary releases is the .py version. If you build LilyPond yourself maybe .pyc versions are created? I doubt if executables are. Have a look in lilypond/usr/bin to see what you have. Here I have just lilypond-book.py. > And if yes, that you have to use 'which lilypond-book.py' on Windows? Seems so. which lilypond-book returns nothing. Remember this is when using the MinGW Bash shell, which has to be installed separately under Windows. "which" is not a known command in the Windows Command Prompt - I've never explored using that for compiling a doc section, or even for running git. Sounds unlikely to work. Maybe it's not worth pursuing this. There are other hurdles to overcome even if we had a working Windows script - installing MinGW, git, the repository, texi2html, etc. I remember spending quite some time getting this set up in Windows. It would probably put off the typical Windows user. Trevor _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond