> Le 5 oct. 2023 à 22:39, Ian West <[email protected]> a écrit : > Dear David (copied to Jean, and Paul,) > You are very kind. I shall give it a go. But I think you will have to > agree that this is some 5 orders (***) of magnitude more complex than > versions: 2.12.3, 2.18.2-1, and 2.20.0. I never would have got into Lilypond > were I starting from here. > > But you raise another problem; arm64 or x86_64? I read elsewhere "An > Apple M1 or M2 processor is also sometimes referred to by the architecture > name of aarch64 or arm64." Or maybe it does not matter.
Even for Apple Silicon (M1/M2, aka arm64, aka aarch64), the official downloads from lilypond.org are built for x86_64. They can still run on Apple Silicon thanks to the automatic emulation that is done by the system. Consequently, when you follow the official installation procedure, you do *not* have to choose between x86_64 and arm64 since the only choice is x86_64. (Providing native arm64 executables officially would be nice, since these could be faster on Apple Silicon than x86_64 emulation, but the machine we currently use for macOS releases is x86_64.) > Following the MacPorts route, But why do you want to follow the MacPorts route now? You are not solving problems here, only creating problems. MacPorts is great for terminal aficionados. If you are not such a person, stay away from it. > I hit a bump. "Last login: Thu Oct 5 14:05:17 on ttys000 > ianwest@Ians-MacBook-Air ~ % sudo port install lilypond > Password: > Error: > Error: No Xcode installation was found. > Error: Please install Xcode and/or run xcode-select to specify its location. > Error: > Error: Port lilypond requires a full Xcode installation, which was not found > on your system. > Error: You can install Xcode from the Mac App Store or > https://developer.apple.com/xcode/ > Error: Follow https://guide.macports.org/#project.tickets if you believe there > is a bug. > Error: Processing of port lilypond failed > ianwest@Ians-MacBook-Air ~ %", > and do not know why this is required. Perhaps I am being naive; should I > download a zipped lilypond package before trying to install it? Or is it > integral to the MacPorts business? Well, I tried that, placing the unzipped > download in the same directory as the MacPorts, but with the same result > (needing the full set of tools). This makes no sense technically; the archives you download from lilypond.org have nothing to do with MacPorts. Again, just forget about MacPorts. > So I started to download the mentioned "tools"; but when I was told it would > take 43 hours I aborted. > > > (*** The installation of version 2:24.2 assumes that I know how to use > terminal, No, it does not. Nothing on https://lilypond.org/doc/v2.24/Documentation/learning/graphical-setup-under-macos.html mentions a terminal. > how to use MacPorts, No. > know the difference between arm64 and x86_64 No. > (all I know is that I am using an "Apple M2 chip"), difference between a > tar.bz2 package or a tar.gz one, No. Why? > that "darwin" mean "MacOS", Again, no. When you go to https://lilypond.org/download.html , it says "macOS". I only mentioned the meaning of "darwin" because you went looking into the **previous** download website (that for LilyPond before 2.23.6), which used this terminology. > and much more. Compared with simply clicking, or double clicking. a zipped > package.) For what it's worth, I have recently implemented auto-installation of LilyPond in Frescobaldi. This means that after the next Frescobaldi release (hopefully soonish) the procedure will look more like "download the Frescobaldi .app and double-click to open, get a screen proposing to install LilyPond, click OK, done". That's about as close to easy you can get without reintroducing all the technical problems linked with the old "LilyPond.app" packaging.
