Understand what the error is saying what did I miss?
-
@JamesC Have you checked the macOS Deployment Target in the Projucer file? Check under the Release section (or 'Release with Faust' if you're using it).
It should be set to 10.13, but it looks like you have it set to 10.09
-
@bendurso thanks for this just been in and checked it was set to 11.0 I did on the off chance change it to 10.13 but still defaults the same error code
-
@JamesC did you clean the build after making that change?
-
@d-healey yes I ran it twice and double checked that cleaning each time, no matter what I do and despite what it says in the projucer box it says it doesn't fall between the parameters, so still a bit confused!
As before it is no doubt something I've not done or missed that's caused it, hopefully I can get it sorted mac side!
-
I noticed the version error is here for a long time, where xcode says 10.9 is not supported. But usually it automatically sets it to the upper next compatible version. So why suddenly xcode doesn't want to increase the version I don't know...
Perhaps an xcode version issue? Here it's fine on 15.4. I mean, I have the warning but no error, the build works
And maybe it is the time to increase that minimum version Hise is outputting? 10.9 is 2013's Mavericks...
-
@ustk Could be my xcode is currently 16.4 at this time so maybe the issue is related to something like that
-
So the plot thickens...
Going back this morning to check again that the macOS Deployment Target in the Projucer file was correct i now get something new I haven't seen before:
- The Path to your JUCE folder is incorrect
- A new version of Juce is available
Now I'm assuming that the new version isn't a massive issue just yet but I imagine the path to JUCE folder is fairly critical what should it be is it the JUCE folder in the HISE standalone build?
I noticed it had a reset to default so I did that and even that brings the same error:
- The Path to your JUCE folder is incorrect
-
@JamesC when you see those messages, click don't ask again. They can be safely ignored
-
@d-healey ok thanks
-
Hey Guys just to give some updates to this, for sure an xcode issue, I pulled my old mac mini out (Sonoma 14.7.7) and compiled on that and had the same issues come up until I went back to xcode 15.0 and was able to get completed functional vst and au builds out!
Cheers for all the help
