On 28/05/11 17:16, Graham Percival wrote:
> On Sat, May 28, 2011 at 04:54:57PM +0100, Phil Holmes wrote:
>> ----- Original Message ----- From: "Graham Percival"
>> <[email protected]>
>>> Why not redirect the compile-output from each .ly to the
>>> appropriate .log file? I mean, we *already* have a .log for each
>>> .ly file... what's in the .log file at the moment? Why not put
>>> the --verbose output in there? etc.
>>
>> Don't believe there is a log file. Can't see one, anyway.
>
> huh, you're right. I just assumed that dirs like
> build/out/lyubook-db/??/
> would have .log files as well as all the other stuff that's there.
> Well, that makes the overall strategy easier. :)
>
>> I know Lily sends output to the console by default. What causes
>> it to write logfiles instead?
>
> You, please. :)
>
Or use the code for lilypond -dgui
gui (#f) Run LilyPond from a GUI and redirect stderr to
a log file.
Cheers,
Ian
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
