Xcode 12.2 ?
-
Hello, so I know this topic is covered all over the place here but I can't find my answers. as I am a real lumberjack, I broke the motherboard of my mac mini on which I had all my projects. It's okay, I have a backup;) my question is about xcode 12.2 . according to the apple developper team, for an audio unit plugin to work on M1 processors, it is imperative to compile with the binary Universal option of xcode. in fact this manipulation is only necessary for software developed by apple (LOGIC PRO). so previously i was compiling with mojave and xcode 10.3 and notarizing. the plugins work well under bigsure and m1 processor on all software except logic. so my question is: is there a way to compile hise with x xode 12.2 catalina without getting 50 semantic issue error? according to my research, no plugin compiled from xcode 10 will work with logic pro under m1 processor. the rosetta solution will in fact, with logic pro, make any plugin usable. I said that everything works outside of logic pro. what solution did you have apart from going to fight me with the engineers at logic pro?
-
Like i answered you in previous topic. I have M1. I can build plugin on Xcode 10.3 and these plugins work on intel and m1 silicons.
-
@arminh Do they work in Logic Pro on Big Sur?
-
@arminh I'm only talking about audio units for logic pro. my plugins work fine once notarized on other software. sorry for the translations if it doesn't transcribe exactly what I mean ^^
-
@d-healey @arminh I found it. I think it is mandatory to compile with this binary mode to work with logic pro.
I really wanted to try but compiling from xcode 12.2 is not possible
https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary -
@d-healey yes without any problem
-
@arminh You're building on your M1 machine or on an Intel machine?
-
@d-healey on m1
-
@Yall is building on an Intel system I believe.
-
@d-healey yes i am on intel. bigsur x code 12.2 but there are too many errors for me to write to you. but to put it simply. semantic issue error everywhere everywhere ^^
-
@arminh Can you, if you want to explain to me how you did it? I think in the future many here will need to know because the usual method does not work
-
I would not build a VST for all the architectures of macOS with anything but X86_64 as the architecture flag in JUCE. If the newer architectures is to be used, make another separate .au for that. That way the newer architectures can have more optimizations. But I have not yet seen a HISE version with a compatible JUCE that handles ARM for macOS. That is only as I have seen it for Linux OS:es.
If you were to use an ARM based M1 mac, that should probably be set to Architecture = Native of Build System. But exporting and compiling directly form HISE is the mistake there, you have to stop the compiling in terminal (ctrl + c) and then open the exported .jucer file and modify, save and then run the .sh again when either having set Native or Standard X86_64 as the architecture. Or HISE will do whatever is default, which is unique to the OS and version of JUCE, as stated many times in the JUCE forums.
-
@andioak it seems to me that the latest version of hise supports arm. but my problem is not yet there. i am unable to compile hise with xcode 12.2 at first. i am with bigsur
-
@yall ouch, okay. I missed that fact. Please let us know of the outcome of your tests.
-
@andioak for the moment there is nothing. I still haven't managed to compile hise ^^
