Have you explored getting JUCE 7 working on the latest OS? I can think of at least five things that might be worth exploring
-
If you have a JUCE 8 licence grab the few commits from the JUCE 8 branch and apply them to JUCE 7 on a fork. I posted the commits I expect you’ll need here.
-
If you don’t have a licence, look at doing the work yourself. In this case I think it could be done with ignoring a few warnings and returning a null image for a single function, as long as you don’t need
juce::createSnapshotOfNativeWindow()to work. -
Try to get Xcode 16 to point at an older macOS SDK. This was a common task that was carried out with older Xcode versions (at least in my experience) see this question on StackOverflow where someone is asking about this
-
Some have reported success using Xcode 15 on the command line in macOS Sequoia, maybe this would suffice in this case
-
Install Sonoma on a virtual machine to allow development to continue on the older OS, something like VirtualBuddy might be useful for this
I would also add that in my professional experience I would strongly advise against updating to the very latest OS and tools versions on an active development environment wherever possible, esp. if some kind of deadline is looming. By all means have an up to date test environment, and even better a secondary development environment that you can use to evaluate the state of things. However, my general rule of thumb is don’t update macOS or Xcode on development environments until the following beta version is out unless absolutely required. That being said I understand that there are times when your hands are tied and there is no avoiding it.
I will also add that although there are breaking changes moving from JUCE 7 to JUCE 8 we react to issues on the development branch relatively fast and try to keep that branch as stable as possible. I would say more times than not upgrading to the development branch fixes an issue that someone is reporting. Plenty of users have reported using JUCE 8 with success.