|
From: | Aaron Hill |
Subject: | Re: Lilypond not generating PDF |
Date: | Mon, 04 Jul 2022 19:25:59 -0700 |
On 2022-07-04 5:49 pm, Aaron Hill wrote:
On 2022-07-04 5:07 pm, Andrew Bernard wrote:I'm sorry, I don't understand this. Dragging test.ly on the desktop to the LilyPond icon on the desktop fails to produce the PDF output. Both on Windows 10 and 11.That is a different issue than the UAC drag-and-drop limitation that was mentioned. Elevated permissions is almost certainly a red herring, and something bigger is likely being masked. I will take a look and see what is going on. Just give me some time, as I will need to set up a test environment first.
As expected, elevation is masking an underlying issue.The desktop shortcut is wrong. It specifies a start directory of "C:\Users\Public\Desktop" which is coincidently the location in which the shortcut is created. The public desktop is a special directory transparently replicated to all individual user desktops. By design, it does not offer write permission to users.
LilyPond is failing to compile because it attempts to create a temporary file at that location. Open question: Why is LilyPond not using the %TEMP% directory for such things?
Leaving the start directory field blank within the shortcut appears to fix things.
-- Aaron Hill
[Prev in Thread] | Current Thread | [Next in Thread] |