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
Am 18.04.2013 15:10, schrieb Trevor Daniels:
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
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 -
Am 18.04.2013 16:10, schrieb Trevor Daniels:
Urs, you wrote Thursday, April 18, 2013 2:49 PM
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
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
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
Am 18.04.2013 18:20, schrieb Trevor Daniels:
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)
