Hmm... Hopefully we can find download links for 9.6.1, for the community versions?
I'll gladly do the file swap thing, to make it into the 'lite' hack if you can find them.
Currently doing this from a phone, and it's hard work.
The nice thing is, because 9.6.1, 9.6.2 and 9.6.3 are all community versions, we can compare between them and probably port any bug fixes over to 9.6.1 from 9.6.3 whilst not losing 32bit build targets for MacOS X. I'm keen not to lose any bug fixes that might be available to us.
You could then rightly say we are supporting more macs than might currently be on the Sonoma beta.
(Just that we are supporting more macs with OXT than LC are... but in the other direction)
I had another idea about Sonoma. If you could do a system snapshot of Sonoma before installing xcode 14, then compare what files get added after installing xcode, you'd then have a pretty good idea of what was tripping up OXT, by comparing what was missing beforehand.
Either that, or use something like Pacifist to inspect the installer package of Xcode and see what system components are added.
You'd then know what to correct at the OXT compilation stage... A lot of work and definitely a case of detective work to figure that bit out. That approach might work though. Seems logical to me at least.
Hmm... Hopefully we can find download links for 9.6.1, for the community versions?
I'll gladly do the file swap thing, to make it into the 'lite' hack if you can find them.
Currently doing this from a phone, and it's hard work.
The nice thing is, because 9.6.1, 9.6.2 and 9.6.3 are all community versions, we can compare between them and probably port any bug fixes over to 9.6.1 from 9.6.3 whilst not losing 32bit build targets for MacOS X. I'm keen not to lose any bug fixes that might be available to us.
You could then rightly say we are supporting more macs than might currently be on the Sonoma beta.
(Just that we are supporting more macs with OXT than LC are... but in the other direction) :lol:
I had another idea about Sonoma. If you could do a system snapshot of Sonoma before installing xcode 14, then compare what files get added after installing xcode, you'd then have a pretty good idea of what was tripping up OXT, by comparing what was missing beforehand.
Either that, or use something like Pacifist to inspect the installer package of Xcode and see what system components are added.
You'd then know what to correct at the OXT compilation stage... A lot of work and definitely a case of detective work to figure that bit out. That approach might work though. Seems logical to me at least.