Re: Location of output files

[Jenifer Tribe]

This makes sense, thanks.

I've just been right clicking on a .ly file and 'opening' it with lilypond, which is sat in C:\windows\Program Files (x86)\LilyPond, just as you suspected.

So I'll move it to a non-systems area and try running it from there. I need to catch up on windows 10 approach to paths etc.

---

From: Aaron Hill <lilypond@hillvisions.com>
Sent: 29 July 2020 21:39
To: Jenifer Tribe <jonathan_tribe@hotmail.com>
Cc: lilypond-user@gnu.org <lilypond-user@gnu.org>
Subject: Re: Location of output files

 

On 2020-07-29 10:54 am, Jenifer Tribe wrote:
> I've been using lilypond for some years, currently on windows10, and
> version 2.20.
> This directs the output to
> C:\Users\..\AppData\Local\VirtualStore\Windows\SysWOW64.
> Is there a registry entry to change this?

This would appear to be a working directory issue.  Would you kindly
confirm how you are invoking LilyPond?

It would seem you ran LilyPond from C:\Windows\System32.  However,
LilyPond is a 32-bit process and would trigger WOW64 file system
redirection, mapping the working directory to C:\Windows\SysWOW64.  Both
system directories are protected and attempts to write to them trigger
virtualization, mapping the effective working directory to the
VirtualStore location you cited.

Running LilyPond from within the directory where your sources files live
is the simplest option, assuming you want the output to sit along side
the input.  Alternately, you can use the --output command-line option to
be explicit about the target file or folder.


-- Aaron Hill