Looking at Andreas’ binary, you would need to add the following frameworks to match what Troed produced for the download and nightly binaries:
- CAPSImage.Framework (I do not know if Mac users would even notice if IPF support was missing. IPF files appear to be much more popular in the Amiga world. When Nicolas added STX support, I feel it eliminated the need for IPF support).
- Portaudio.Framework (I think it is used for the microphone support on the Falcon. I do not emulate a Falcon so I am not sure about this)
- Portmidi.Framework (allows better MIDI support on Hatari which is used by Mac Hatari users)
- libncurses, libreadline (I think these are both used by Hatari’s debugger. Since you have to activate the debugger from Terminal and run the executable and not the application package, I am not sure how many Mac users use the debugger. However, I know Hatari’s debugger is widely used.
On Apr 26, 2023, at 2:09 AM, Chris Jenkins <cdpjenkins@xxxxxxxxx> wrote:
Cool, sounds like we are getting the same behaviour then.
I need to find the time to build the binary myself using Andreas's approach. That won't happen until the weekend, though, because I'm travelling for the rest of the week. If I can build it myself then I can try to figure out how to sign the app. (I now have an Apple Developer account... I thought screw it, I'll pay £80 and see if that helps... but I am a massive noob when it comes to this stuff so have to learn how it all works.)
This binary shows a different message than I usually see for an unsigned application. However, as you mentioned, as soon as I did “xattr -c <app bundle>”. The program only asked me for permission to my Documents folder (where my GEMDOS disk directory is located) once. It also asked for permission to my Downloads folder (where the binary was located).
Hopefully, the automated nightly binary can be made to work like this.
I've tried the right-click open method multiple times on two different Macs. Same result on both, alas.
I will try the binary when I get home, but did you try opening the binary twice with the right-click open method? I have had luck doing this in the past with non-developer certificate signed applications.
On Tue, Apr 25, 2023, at 11:59 AM, Chris Jenkins wrote:
Great! Isn‘t it possible to open it using right click - open?
No, if I don't remove the quarantine attribute then it isn't even possible to right click and open :-(
Yes, that launches successfully (on my M1 Mac).
I had to use xattr to remove the com.apple.quarantine attribute before I could run it (MacOS tells me that it's "damaged" if I don't do that!) but it then ran fine.
I don't see repeated requests for permissions either :-)
Indeed this is why I sponsored Hatari with a cert for my builds.
Let me see how to handle forwards.
On 23/04/2023 22.38, Chris Jenkins wrote:
> > It works, with caveats:
> > - Hatari starts ok if I right click and click Open. It's unsigned so
> I have
> > to open it that way.
> That only happens during the first time you run the app, right? Or does
> that happen every time you try to run the app?
> This happens every time I run the app.
> One thing I should add: this Hatari binary asks for permission to use my
> microphone every time that I launch it :-(. So I assume that's another
> permission that has to be granted every time that the unsigned app is launched.
Hmm, this all sounds like providing unsigned apps is too annoying nowadays
on macOS. I guess I should rather stop my experiments with cirrus-CI here
and let somebody else handle the macOS builds instead who has a proper
developer ID from Apple. (And no, I certainly won't get one on my own - I
certainly won't pay 99$ a year for something that I'm not using on my own)
You don‘t need a paid ID for signing. Just follow the instructions from my previous message and you will end up with a distributable binary. It will only ask once for every permission (first start, first time microphone used, first access to certain folders).
Any issues with this binary for macOS (universal binary, macOS 10.13 or later, PNG and SDL2 included)?