Hi,

Just to add, it would also be useful to know a bit on the reasons for dropping the older OSes, what exactly are the tehcnical reasons for it, as within macports we have a number of build options available to us, like newer builds of the compilers which can be used instead of the Xcode versions, that help us support a lot of ports on systems way older than upstream for them officially support.

cheers Chris

On 05/04/2023 2:02 am, John Hoyt wrote:
Renee,

Thanks for the pointers - I'll take a look with fresh eyes tomorrow. I've added a todo list in the PR, as it's very much a WIP - although I have been able to successfully build all subports locally (still have to test and attempt to build on arm).

Just a heads up - Qt6.5 seems to be a little different than the work we've done on Qt 6.2.  Some of the qt5 based CMake updates seem to no longer be necessary (and in some cases now break things forcing incorrect paths).

Regards,
John



On Tue, Apr 4, 2023 at 8:39 PM Renee Otten <ottenr.w...@gmail.com <mailto:ottenr.w...@gmail.com>> wrote:

    hi John,

    Thanks for working on that! Regarding the support of older macOS
    versions: The Qt5 PortGroup and ports are the example on how this
    was done for Qt5 and likely on how to do the same for Qt6.

    I likely will not have time to do much work on this myself but will
    look at the PR and see if I can provide some help…

    Best,
    Renee

    On Apr 4, 2023, at 8:32 PM, John Hoyt <john.h...@gmail.com
    <mailto:john.h...@gmail.com>> wrote:

    
    I've started working on updating the qt6 port to qt 6.5.0 (see
    https://github.com/macports/macports-ports/pull/18186
    <https://github.com/macports/macports-ports/pull/18186>).

    Qt 6.5.0 removed support for macOS 10.14 and 10.15, only
    supporting macOS 11 and newer whereas qt 6.2 supports macOS >= 10.14.

    Any suggestions on how to handle the deprecation of macOS 10.14
    and 10.15?

    Thanks,
    John

Reply via email to