Since 10.14 and 11.0 isn’t supported and tested by the development team, don’t forget to backup first…
The packages aren’t codesigned so you might run it first time via right mouseclick + open or allow execution via terminal: " xattr -c <path/to/application.app> "
Just curious. I looked at the sources on github and saw that there is a minimum Xcode version required to build darktable. Fair enough. But builds using the oldest supported Xcode version can target older versions of macOS. Is that how these unofficial packages are built?
I’d hazard a guess that testing against older OS releases is the reason the official darktable release cuts off macOS releases older than 13.5. As someone who’s had to develop and maintain cross-platform software, and is paid to work on software to be delivered on gcc 4 (!), I can understand that choice, even if it inconveniences me as a user.
The Xcode version will support a certain range of macOS SDK’s each of which have their own range of supported deployment targets. Therefor it is definitely possible to deploy to an older system than the build machine.
using macports you can give a macOS deployment target. Recent XCode supports builds with a deployment target 10.14.
But that also depends on the code requirements of used libraries - e.g. the latest exiv2 v0.28.3 library requires at least macos10.15.
The nightly builds are done using homebrew - but there there’s no way to build for an older deployment target. GitHub macOS arm64 runner is macos14.
So these builds as well as the official 13.5 build is done with macports and giving a proper deployment target instead of homebrew…