My guess here is that not many folks use WSJT-X on Macs.   :)

I wanted to see if anyone else has attempted to build WSJT-X for M1 Macs?  

I’ve managed to build the entire source using the latest compilers and even got 
it to link with a bit of hacking on the M1 (mostly around bogus -Xclang arg 
being sent to gfortran and missing __chkstk_darwin() symbol in wsprd.c only on 
M1).  

I’m working on some issues getting the app to launch.  With the more modern OS 
(MacOS X 12), signing is required and I’m running into some issues there.  It 
seems that there might be some signing going on by default that’s causing the 
app to get killed on launch with a EXC_BAD_ACCESS (SIGKILL (Code Signature 
Invalid)).  As a result I tried signing the app manually by replacing any 
signature that was there using a provision I created.  ‘codesign -vvvv 
wsjt.app’ reports wsjtx.app: is valid on disk — wsjtx.app: satisfies its 
Designated Requirement, but the OS doesn’t agree.  It might need to be 
notarized as well.  spctl reports './wsjtx.app: invalid signature (code or 
signature have been modified)’ which is kinda true.

I wanted to reach out and see if anyone else has tried to build for M1 and 
possibly ran into this.  I realize I still have a long way to go considering 
I’m using the latest gfortran which is known to be incompatible. But I figured 
I’d deal with that once I got the app to launch!  Baby steps... ;-)

The M1 Mac is ridiculously fast at compiling this source so I can imagine it 
will decode FT8, etc. with ease.  Plus at some point we should make this work.  
heh…

Anyway thanks for everyone’s help so far with building WSJT-X for Big Sur (I 
finally have that working).
best,
alex K6LOT



p.s. I’ve been keeping notes and will publish the steps necessary to build 
WSJT-X from the tarball on M1 or any Mac (including all the packages to install 
via Brew) if anyone is interested.

p.p.s. I also wanted to follow up and say that the issue with App Napping was 
resolved, John (G4KLA) and I verified that disabling the local app napping 
setting gets rid of the problem with failed decodes when in the background and 
the system is under load…  I understand our workaround has been added to the 
Mac Readme but I have not verified that yet or tested the steps.  Been too busy 
trying to get 2.5.0-rc5 to run on my M1 MacBook Air. ;-)



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to