Develop branch build status
I was able to succesfully compile on Windows 10 running in a virtual machine. I used VS 2019 and retargeted the HISE solution file inside VS.
I was able to successfully compile on Big Sur with Xcode 12.5. The deployment target version must be a minimum of 10.14. The build architecture should be set to Native.
I don't have IPP installed but I see no reason why it shouldn't work. I built with FFTW3 shared library installed through home-brew.
Compilation and linking works. I had to make a few modification to the HISE source, these have been pushed to GitHub and a pull request to Christoph's repo has been made.
Windows 10 : sucessfully compiled using VS 2017.
MacOs : successfully compiled on Catalina using Xcode v.10.3. I ran across some errors/missing stuff but managed to do it. (If someone needs info I can try to look back and tell more).
Linux : I don't have a Linux system yet
I'm waiting for xcode 12 support
@d-healey OSX Mojave 10.14.6, XCode 10.3
Worked like a charm :) Didn't have to change anything
@d-healey i tried build with 12 but i had some issues
Windows10 VS 2017 => no problem (except I found out I'm an idiot...)
macOS High Sierra, XCode 10.1 => no problem
Mojave 10.14.6 and Xcode 10.3, no problems here.
macOS Catalina (Intel)
Fails with XCode 12.3
macOS Catalina (Intel)
Successful with XCode 10.3
Successful with VS2017 (NOTE: Update might be needed, I updated the VS2017 to the version 15.9.36)
Is there something to do because as I had specified on the final roadmap thread, I successfully compile without any error message and my vst instrument does not open in the daw. I did as usual and could not display the vst. the daw tells me it is not properly installed. I do not understand
@yall Make a new thread and give more details
Big Sur - develop branch
Almost there but it falls at the last hurdle.
You are trying to build HISE for native ARM, this is not supported. Just select Rosetta as build target in XCode, then it should succeed.
HISE must run under Rosetta - only the exported plugins will be native M1.
@Christoph-Hart Yeah I just realised that after I posted. I switched the architecture to native (I'm on Intel) and it built just fine. Maybe this should be set as default in the juicer file? I also had to change the minimum version to 10.14.
I think I've made some local changes to the Projucer file to build on M1, but I'm not 100% sure if it can be the default (IPP is deactivated and their build flags are removed), but in the long run I'll try to make it compile from the default settings...
@Christoph-Hart I'm building on Intel.
Yes, that's right, it doesn't matter which architecture, I just hacked something together to make it build on my Macbook M1.
This post is deleted!
Mac OS Big Sur Intel: Updated
Compiled Successfully the Latest Develop ( 22-07-2021) under Big Sur 11.1
on a Mac Pro 4.1 Flashed to 5.1
i Used Xcode 12 and also installed Command_Line_Tools_for_Xcode_12 from
September 17 2020
(i tried this morning with Xcode v12.5.1 it did not compile too many errors
so use "Xcode 12" from September 17 2020)
and Intel oneAPI BaseKit (for ipp)
Intel oneAPI Base Toolkit
for ipp i had to move the ipp folder one level up under intel because the installer does not put it where hise needs it!!
Installation of IPP
Select Custom Installation:
Select Intel Integrated Performance Primitives Only!
Go to opt/intel and move the ipp folder up one level under intel!
Oops! i Forgot you have to open the ipp folder
this is how it has to be to Work!
Success! Exported Stand Alone App VST And Audio Unit and Everything Works! Under Intel
( P.S. i did not Test Under M1 i do not have a M1 Computer Yet!)