I tried running 0.4.10+ (build 2022-03-14.fd3ef5f) on an M1/AS/ARM Mac with macOS 12.3 and it starts but when I click "Single Player" the button shows the click down state, the music starts but then it all freezes and nothing changes after that (the must stops too). I tried to open and run it in Instruments (comes with Xcode and does profiling) but I couldn't really figure anything out. If I ran it from source that would make it easier but I have never been able to get FreeOrion to compile on my Mac. I tried again just now but didn't get far. I cloned the freeorion github repo and ran the github action that builds FreeOrion so I could get a reference and it's 55 minutes and still compiling.
I just tried previous weekly builds and 2022-03-07.b3df307 works.
0.4.10+ (build 2022-03-14.fd3ef5f) freezes on macOS 12.3 on M1/AS/ARM
Moderator: Oberlus
Forum rules
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Re: 0.4.10+ (build 2022-03-14.fd3ef5f) freezes on macOS 12.3 on M1/AS/ARM
I submitted this too soon. 2022-03-07.b3df307 works, but the mouse action I usually perform to move ships (left click) doesn't work. It works in 2022-02-28.7f6c2e1 though.
Re: 0.4.10+ (build 2022-03-14.fd3ef5f) freezes on macOS 12.3 on M1/AS/ARM
The problem is, I'm the only dev on Mac, my Mac is Intel, and I do not have access to one of the new ARM Macs, so I can't do any troubleshooting for the new platform.
Also, currently the SDK for Mac is set up only for producing Intel binaries, we haven't done any work on adjusting the SDK to produce universal binaries.
Apparently the latest test builds introduced something which makes the binaries produced by the current setup to not work on ARM Macs anymore.
Anyone any idea which of the latest changes (since b3df307) might be the source of this...?
Also, currently the SDK for Mac is set up only for producing Intel binaries, we haven't done any work on adjusting the SDK to produce universal binaries.
Apparently the latest test builds introduced something which makes the binaries produced by the current setup to not work on ARM Macs anymore.
Anyone any idea which of the latest changes (since b3df307) might be the source of this...?