Urs, you wrote Monday, April 15, 2013 5:07 PM > OK, what the heck: > Here is a patch trying to fix the lilypond-book issue in doc-section.sh, > along with a comment in the CG. > If I have time I'll look into the other BUILD_DIRECTORY dependencies. > And if you can confirm my impression I would also make a patch removing > cg-section.sh and the reference in the CG.
I applied this patch and tried to execute the script within the Bash shell of MinGW under Windows Vista, with this result: Trevor@TREVOR-LAPTOP ~/lilypond-git (urs-lilypond-book) $ scripts/auxiliar/doc-section.sh notation pitches $LILYPOND_GIT was not set; auto-detected source tree at /c/Users/Trevor/lilypond-git $BROWSER not set; using firefox as default /c/Users/Trevor/lilypond-git/build did not exist; check your setting of LILYPOND_BUILD_DIR. Aborting. I don't have a LilyPond build directory under Windows, of course. It's several years since I looked at this, but the script now is quite unrecognisable from the one I wrote originally for Windows. It seems it's been hijacked to work under Linux without concern for Windows users. I guess that's the reason I use my own script now. Not sure how we proceed. The default location of lilypond-book under Windows Vista is C:/Program Files/LilyPond/usr/bin/lilypond-book.py Trevor _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond