Marnen, This is a response to an email from more than a year ago. Our situation hasn’t improved since then, even though you did all your great work.
What do you think it would take to make this bundle part of the core project? I agree with you that it should be part of our core. But it doesn’t match up with our current build process, because it cannot be done on non-Apple hardware. I see from some old emails that you envision some sort of CI that builds an app bundle. It would need to have access to Apple hardware to do that, IIUC. Do you have thoughts about how we would get access to that Apple hardware? Thanks, Carl From: Marnen Laibow-Koser <[email protected]> Date: Thursday, April 2, 2020 at 2:18 PM To: Carl Sorensen <[email protected]> Cc: LilyPond Users <[email protected]>, Moritz Heffter <[email protected]> Subject: Re: Lilypond 64-bit binaries On Thu, Apr 2, 2020 at 1:49 PM Carl Sorensen <[email protected]<mailto:[email protected]>> wrote: From: Marnen Laibow-Koser <[email protected]<mailto:[email protected]>> Date: Thursday, April 2, 2020 at 11:07 AM To: Carl Sorensen <[email protected]<mailto:[email protected]>> Cc: LilyPond Users <[email protected]<mailto:[email protected]>>, Moritz Heffter <[email protected]<mailto:[email protected]>> Subject: Re: Lilypond 64-bit binaries On Thu, Apr 2, 2020 at 1:02 PM Carl Sorensen <[email protected]<mailto:[email protected]>> wrote: I note that Moritz mentions he gets the same results from the MacPorts build. Perhaps the MacPorts people could provide some insight. Hmm. I wonder if I should try using a more recent version of Mac OS and Xcode on the build box. I was using the oldest possible version in order to produce the most backward-compatible build. But...if this is a general issue with Catalina, why are so few users affected by it, and why are users on Mojave among those affected? I don’t think it’s a general issue. I think it’s a specific issue, that varies from machine to machine. My only suggestion was that perhaps somebody in the MacPorts group might be able to provide some debugging helps. Hopefully the issue is the same in MacPorts as in your app bundle, so if it can be resolved in MacPorts it can be resolved in the app bundle…. Yeah, that might be a good point. I think this is the first time we've seen a MacPorts build have this same problem. Also: it's not *my* bundle, except in that I figured out the process to build it. Ideally, it is the LilyPond project's bundle: I want this to be accepted into the core project, not remain my own personal thing. Carl Best, -- Marnen Laibow-Koser [email protected]<mailto:[email protected]> http://www.marnen.org
