13 | | It would be a workaround. The better fix would be to backport the changes that make Xcode usage optional to older Qt5 versions (since, like previously said, Qt5 has a habit of deprecating macOS versions quite aggressively, so that older platforms are forced to use older, unmaintained Qt5 versions). I don't know how much effort that would be, though. There were definitely changes to that one file, which are crucial, but we might need even more changes to make it work **correctly** (see opportunistic compiler usage, which [UsingTheRightCompiler is not what we want]. |
| 13 | It would be a workaround. The better fix would be to backport the changes that make Xcode usage optional to older Qt5 versions (since, like previously said, Qt5 has a habit of deprecating macOS versions quite aggressively, so that older platforms are forced to use older, unmaintained Qt5 versions). I don't know how much effort that would be, though. There were definitely changes to that one file, which are crucial, but we might need even more changes to make it work **correctly** (see opportunistic compiler usage, which [UsingTheRightCompiler is not what we want]). |