Universal Binary Issues
-
Hi all back again with another issue but as always could be me!
So complied HISE on Sonoma 14.7.7 (Intel Core i3) with xcode 15 and compiled vst3 and au that runs great on this intel machine. However it fails to run on any silicon systems. Now looking back over the output of the compile of the plugin I can see this warning:
FRESH TEST - Shared Code] Create Universal Binary libFRESH\ TEST.a
️ /Users/jamescox/Documents/HISE Projects/FRESH TEST/Binaries/Builds/MacOSX/FRESH TEST.xcodeproj: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.9, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'FRESH TEST - VST3' from project 'FRESH TEST')
MkDir /Users/jamescox/Documents/HISE\ Projects/FRESH\ TEST/Binaries/Builds/MacOSX/build/Release/FRESH\ TEST.vst3/Contents/MacOS (in target 'FRESH TEST - VST3' from project 'FRESH TEST')Now when I went to look at the deployment target (as in a previous post about another system) its set to 10.3 (I assume this is the default I've not changed it) so falls between the range that it suggests.
Unsure if its relevant or not but worth mentioning incase this plugin was built on the PC version of HISE and I ported the files over to run the Mac compile, hopefully thats not the issue!
If anyone can help would be great I'm getting so close to having a plugin that works on all systems (PC, Intel Mac runs real nice) just need to get over this final hurdle but I just can't seem to work out what I'm doing wrong!
-
@JamesC Which commit of HISE are you using?
-
@JamesC Develop if I understand what you mean
-
@JamesC In HISE, go to Help > About HISE, click the Show commit on GitHub button. Then paste the link here so I can see exactly which commit you're using.
-
@d-healey Commit 2159fd5
-
@JamesC Yep, you're using the latest, so that's not the issue.
@JamesC said in Universal Binary Issues:
However it fails to run on any silicon systems.
What happens exactly?
-
@d-healey in any daw on mac silicon system it wont even scan and add it to the plugins list. PC and mac intel as expected appears on the list and can be used in DAW.
Same issue I was having when I was compiling on the M2 Sequoia 15.6 using xcode 16 exactly the same behaviour and error
-
@JamesC Have you codesigned it?
-
@d-healey said in Universal Binary Issues:
codesigned
I don't believe I have dev stuff not my strong point as yet
-
@JamesC That could be why, macOS is fussy about running software built on a different machine that isn't codesigned (sometimes on the same machine).
Here's a workaround you can use while testing: https://forum.hise.audio/topic/11856/unsigned-vst3-issue-on-mac-unknown-developer/5?_=1756056705291
-
@d-healey thanks for the advice as always will give that temp solution a try once the kids are asleep!
Then do some research how to codesign the software on the pc which is where I tend to work then
-
@JamesC said in Universal Binary Issues:
thanks for the advice as always will give that temp solution a try once the kids are asleep!
Let me know if it works.
You can't codesign a Mac plugin on Windows, you need to do it on macOS. You'll need a developer account, it's a bit of a fiddly process the first time you do it. There are a few guides on the forum that should come up in the search.