Re: Testers wanted

[David Kastrup]

Knut Petersen <knupero@gmail.com> writes:

> On 14.07.21 16:09, Knute Snortum wrote:
>> I had problems with a basic ly file.  It looks like the program is
>> trying to open /dev/null and that doesn't work on a windows machine.
>>
>>> lilypond --pdf -dbackend=cairo bach_first_lesson_minuet.ly
>> GNU LilyPond 2.23.4
>> Processing `bach_first_lesson_minuet.ly'
>> Parsing...
>> Interpreting music...[8][16][24][32][40]
>> Preprocessing graphical objects...
>> Interpreting music...
>> MIDI output to `bach_first_lesson_minuet.mid'...
>> Finding the ideal number of pages...
>> Fitting music on 1 page...
>> Drawing systems...C:/Program Files
>> (x86)/LilyPond-2.23.4/usr/share/lilypond/current/scm/lily/framework-cairo.scm:262:16:
>> In procedure open-file in expression (open-file "/dev/null" "w"):
>> C:/Program Files
>> (x86)/LilyPond-2.23.4/usr/share/lilypond/current/scm/lily/framework-cairo.scm:262:16:
>> No such file or directory: "/dev/null"
>
> Please change "/dev/null" in line 262 of  C:/Program
> Files(x86)/LilyPond-2.23.4/usr/share/lilypond/current/scm/lily/framework-cairo.scm
> to the equivalent of /dev/null on windows. What name is used for the
> NullDevice in the supported Windows versions? \Devices\Null? Null?||||
>
> Background: ly:make-paper-outputter assumes that every backend will
> need an output file,  I thought choosing /dev/null would be ok as
> (most of) the output files are  created, written and closed directly
> by the cairo library.

At least the calling convention appears only to assume that every
backend will need an output _port_.  %make-void-port may fit the bill
though I haven't checked.

-- 
David Kastrup