Mojave Xcode 11.1 HISE plugin build failing
-
I think it's a glitch from updating XCode. Googling that error yields many "You need to clear blabla bla after updating to Xcode version blablablabla".
-
Christoph is correct. Xcode does weird caching that results in build limbo (especially between versions :( Clearing derived data is a must) that can cause strange errors, but also Please select Script Node branch (make sure that script node branch is selected -https://github.com/christophhart/HISE/tree/scriptnode ) Script node is the cutting edge build and I've tested AU and Stand Alone in the last 24 h and both should compile without issue on Mojave 14.6 and Xcode 11.1
-
@mwplugs I have the latest scriptnode code (2019-10-18) and all au plugins failed to build when using xCode 11.1.
I cleared derived data but still no luck, so I deleted xcode 11.1 and installed xcode 10.1 instead, and now all plugins build as they should. -
@ulrik Not really helpful, but I have to say it :D I find Xcode to be much more of a pain then Visual ever was... :D
Why so many samples.... ok ... I still need more :D
-
@VHO xcode seems to have a life of it's own, you have to please it with kind words and beautiful code :)
-
@VHO what xcode did you have installed before installing v.11.1?
or was it a first time install? -
@ulrik it was clean install for me. There was no Xcode prior as I did clean Mojave install. I was on High Sierra for ages and I'm not brave enough to go to Catalina yet and probably won't be for a while :D
-
@VHO ok, I guess some strange things happens when updating xcode then, maybe I didn't clean the old installation enough...
-
@VHO said in Mojave Xcode 11.1 HISE plugin build failing:
I'm not brave enough to go to Catalina yet and probably won't be for a while
It's not brave, it's sane :) The number of emails I got from various audio companies (even Native Instruments and Ableton) warning about updating to Catalina is ridiculous. There's even one company (Melda Productions) that seriously considers ditching the entire OS because of the update :)
-
@Christoph-Hart Surely, this is something we'll have to face. Better sooner rather than later.
