Am 18.04.2013 16:10, schrieb Trevor Daniels:
Urs, you wrote Thursday, April 18, 2013 2:49 PM
I will look into it (when I have time) and see if I can manage to make
the script independent from a present build.
It's just an interesting topic and I'll learn something from it.
I suggest you can just wait if I provide something new.
OK - if you can make a more generally useful script it might help
encourage others, especially Windows users, to do some doc work.
I'm working on it - and it seems there are a few things to reconsider.
For example: If the LILYPOND_TEMPDOC variable is set manually, all
output will go there and it doesn't matter if the LILYPOND_BUILD_DIR is
present or not - but the (old) script would stop there anyway etc.
One questions (to those who have built LilyPond):
What does $LILYPOND_BUILD_DIR/Documentation/out/version.itexi refer to?
The script wants to copy it to the output dir.
Urs
Except:
The default location of lilypond-book
under Windows Vista is
C:/Program Files/LilyPond/usr/bin/lilypond-book.py
On Linux I found the location by the result of `which lilypond-book`.
Would that work on Windows too?
which lilypond-book.py works fine in the WinGW Bash shell.
I've just realised in your script you missed off the .py extension,
which would prevent it working.
Trevor
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
