Hi Dirk.

On 30/11/2025 10:34, Dirk Hohndel via subsurface wrote:

 % ls -lhrt ~/Downloads | tail -3
    55M Nov 29 09:50 Subsurface-MacOS-x86_64-qt-5-6.0.5492-patch.43.pull-request.dirkhh-macos.zip   255M Nov 29 09:52 Subsurface-MacOS-arm64-qt-6.10.1-6.0.5492-patch.43.pull-request.dirkhh-macos.zip   255M Nov 29 09:52 Subsurface-MacOS-x86_64-qt-6.10.1-6.0.5492-patch.43.pull-request.dirkhh-macos.zip


Ha, I wish I had something to test this on. :-)
The newest macOS my ancient hardware can run is 12.7.6 - this requires 13. But I think the way to go for this is to drop support for running on macOS versions that have been dropped from support by Apple.

The issue is that the Qt Framework binaries already require macOS 13.
I could try building against an older version of the framework - childishly easy with the matrix setup. Let's see if that gives us a lower minimum OS version.


I am not saying that we should fix this - I see this more as a shortcoming of my setup, running an OS that has lost support for updates (including security) from the manufacturer. In terms of minimising the amount of work that will be needed to maintain Subsurface in the future, it might be a better approach to try and go as far forward as we reasonably can with this version update.



Ohmygawd - it looks like they are bundling an entire browser with this.

At a pinch we could probably include the PDF version of the manual in the bundle, and then just use a system 'open' call for it...

'open' also works on an HTML file. But see my other email about the alternative 'lightweight' browser that some Qt projects have started to use for the same purpose (we're not the only ones with an HTML user manual, it seems)


But then this typically will open a new tab in the user's default browser, which can be confusing if what we want to do is show the user manual that was included with the binary that the user is running.


Ngā mihi

  Michael Keller
_______________________________________________
subsurface mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to