View Single Post
Old 11-26-2023, 11:47 AM   #17
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,948
Karma: 6361444
Join Date: Nov 2009
Device: many
FYI.

All of both Qt 6.5.x and Qt 6.6 can be easily built to target macOS 11 even with the latest XCode tools as the deployment target. I do this for Sigil.

I know of no software that requires macOS 12 as a min target (yet) but I am sure a future QtWebEngine will require it in the Qt 6.X series, just not Qt 6.5.3 or Qt 6.6.1.

Perhaps this is something required for notarization?

That said, only the most recent 3 versions of macOS get security fixes from Apple (in general) so upgrading to the latest version of macOS your machine supports is always a good idea (after the first fixes are released of course). Just for security alone. So just update if you can whether you want the new features or not, the security fixes make that paramount in this day and age.

With a properly set up machine with older XCode you can still build software back to macOS 10.9 timeframe but security-wise it is not worth it.

When my 10 year old iMac could no longer update, I was easily able to completely remove macOS and replace it with Manjaro KDE version and still keep the machine secure and running for another 5 years.

My 2 cents ...

Last edited by KevinH; 11-26-2023 at 11:58 AM.
KevinH is online now   Reply With Quote