FET executable for Mac OS X, by Darren McDonald

[Darren McDonald]

Hi deewahyu, sorry for the late reply!

I've got a few older versions that might work, but I can't tell you which you'd need.

Try one of these (try them in this order, so you get the most current working version):

• FET-6.3.4
• FET-6.2.8
• FET-6.1.8

Good luck!

[BismaBRJ]

Hello, I simply want to confirm that the provided precompiled FET-6.3.4 works for my macOS 10.14.5. Thank you very much, Darren!!

[gt]

Hello. I still have to run on older Macs. Occasionally I compile with Qt 5.13.0, it seems to allow running newer Fet versions on old MacOs.
I just compiled v.6.18.1. I'd share it (hoping to be helpful to other users) so please let me know if it could be uploaded somewhere.
Regards

[Liviu Lalescu]

Hello, @gt ,

Thank you for your work!

Maybe you could also try Qt 5.15.v (5.15.2 is the latest freely available binary, 5.15.12 are the latest freely available sources). It will certainly run on old macOS.

Please see how we link Darren's page on the FET download page. If Darren agrees, I could also add a link to your page, with something like "macOS executable, by gt, for older mac-s". If you don't have a page, it is a bit problematic.

I am opened to discussions.

[ayreon]

Hi,
I use Fet for MacOS regularly but now I'd like to use also the cli version and I noticed that there is no fet-cl in the MacOS version. I compiled it myself but I need to do every time a new version come out,
is it possibile to have the cli executable inside the built package on the web site?
Thanks!

[Liviu Lalescu]

Hello, @ayreon

Thank you for your interest! I will kindly ask @Darren McDonald to have a look at your post.

[Volker Dirr]

Nice answer:
Thank you for suggestion. It's a good suggestion.

***
Only read if you like sarcastic comments:
yes, moving (the unpaid) work to an other person is always the easiest part.

Ok. you are probably right, it won't be too difficult if you already compile the GUI version. On the other hand I hope more people will think more about all that work. Not only coding, compiling, helping in the forum, pay the web server so people can download for free, ... I hope people will not forget to donate at least a bit, so we can pay at least web server, current, ... . And also hardware/software that we only bought so we can compile and test on that other hardware/software that we don't use in normal case. We only bought it, because other users use it.

[ayreon]

Yes, you're right, but...
I would not have asked if it would require some effort.. I mean, I followed your guide to compile a macOS version and the fet-cl executable was there, I just copied it inside the fet.app folder.. There's no need to do anything else. So I was wondering if, since you already compile a macOs version and put on the web site, maybe with an automated script, maybe it could be possible to add the copy of that file inside the package. :-)
For everything else you said your're definitely right.
Thanks for all your works

[Darren McDonald]

ayreon, you're right that compiling FET produces both the app and the cli version, and we used to bundle the cli version with the app.

Unfortunately, the introduction of Gatekeeper (Apple's OS "feature" that ensures only "trusted"* apps can run) complicates things. I'm guessing you only ran the compiled cli on the Mac you used to compile FET? If so, you wouldn't notice any issues. However, if you try to run the cli version you compiled on any other machine, you won't be able to get it to run (at least not with ease). There are some workarounds (they require some terminal commands to recursively mark the components of the script as trusted), but it's a pain to do (and may not even work on the latest OS), so I figured that anyone who wants to use cli version of FET (a minority of FET users) would also be someone who could compile the software without difficulty on their own machine, so I dropped the cli version from the mac bundle years ago, and I think you may be the first person to have have noticed.

In any case, it looks like you've managed just fine, so it's good news that the cli version is still working on macOS!

*To some extent, "trusted" just identifies those who have paid Apple for an Apple Developer account at (when last I checked) $100 per year. I think Mac users can decide on their own whether they trust the FET developers enough to run the software.

[ayreon]

Hi Darren, thanks for your answer, I didn't know about this critical technical limitation!
Yes the fet-cl compiles just fine on an M3 Pro with latest macOS.
I can also add that I compiled the fet-cl using your guide on that M3 Pro machine enabling also the use on an Intel processor (so that I can use it also on a mac Mini), and it worked just fine on that machine. But I do not know if it is because the mac mini (2018) is old or because they are linked to the same account.
I thought it was easier but if there is a problem with the security for the majority of the users, of course, I'll continue building it on my own :-)
Thanks for all the good work.