[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Installation of Lilypond 2.24.0 on a Windows 11 computer
From: |
tommy_strandberg |
Subject: |
RE: Installation of Lilypond 2.24.0 on a Windows 11 computer |
Date: |
Tue, 7 Feb 2023 20:03:34 +0100 |
Hi,
As I already said, I'm not an expert in this so it's more a solution partially
on trial and error.
For information, I've never changed anything while installing any program,
Frescobaldi or Lilypond on my almost new Windows 11 computer. V2.22.2 was
obviously installed using the installer which by default put it into C:\Program
Files (x86). The same happened with Frescobaldi. The version 2.24.0 I, at
first, uncompressed into my "home" directory
C:\Users\tommy\Documents\_DellDaten\60_Programs\Lilypond as suggested by the
manual and in Frescobaldi linked in the 2.24.0 version under preferences as
written in the manual but I kept the link to v2.22.2 and declared 2.24.0 as
default. By the way, v2.22.2 still worked without any error messages despite
the problems with 2.24.0, but now it's uninstalled of course.
I've now uninstalled 2.22.2 and reinstalled Frescobaldi, and uncompressed
2.24.0 into the same directory, i.e. C:\Program Files. I don’t' know why, but
now it works without error messages.
I fully agree, It's no good to install anything with admin rights into
C:\Program Files or C:\Program Files (x86).
I'll try your suggestion tomorrow but anyway, thanks for the help.
BR
Tommy
-----Original Message-----
From: Jean Abou Samra <jean@abou-samra.fr>
Sent: Tuesday, February 7, 2023 7:43 PM
To: tommy_strandberg@web.de; 'Paul Hodges' <pwh@cassland.org>;
lilypond-user@gnu.org
Subject: Re: Installation of Lilypond 2.24.0 on a Windows 11 computer
On 07/02/2023 19:25, tommy_strandberg@web.de wrote:
> 2. The handbook is very misleading as it states (
> https://lilypond.org/doc/v2.23/Documentation/learning/graphical-setup-under-windows
>
> <https://lilypond.org/doc/v2.23/Documentation/learning/graphical-setup-under-windows>)
> “Place the resulting directory lilypond-x.y.z-mingw-x86_64 in a permanent
> location; the actual folder doesn’t matter; you just need to put it somewhere
> you won’t move it afterwards. For example, you could choose your home folder.”
>
> With the experience of today and my problems, this seems to be
> completely wrong and should be updated.
I disagree. There is no obvious reason why it should be so.
That section from the manual was written by me, and as the screenshots show, I
tested the installation procedure step by step, and it worked.
I definitely did not install anything into C:\Program Files or C:\Program Files
(x86) and I would recommend against doing so (there is a reason why it requires
admin rights). You are also the first one to report this problem, two months
after the release of version 2.24.0, which means it is working for other people.
I don't know if the install location has anything to do with it, but LilyPond
is supposed to work while installed anywhere. If it doesn't, there is a bug
either in LilyPond, or in Fontconfig (the library LilyPond uses to search
fonts), or in your setup (it could have been messed up by a completely
different application), but not in the documentation.
Which brings me back to the question about FC_DEBUG.
Regards,
Jean
Re: Installation of Lilypond 2.24.0 on a Windows 11 computer, Jean Abou Samra, 2023/02/07