Develop branch build status
-
@nouslou I don't have an M1 system and I don't use IPP so I can't confirm that. What I suggest is you start off by compiling without IPP, use the new_layout branch, and use xcode 13. Once you get that working then try building with IPP.
-
@d-healey so, I managed to compile new_layout branch with Xcode 13 and IPP (x86_64) on my M1. But got every time those errors when open Hise:
But when I trying to export vst/au I every time get this:
P.S. and when I trying to create an interface - it's crashes. All the time. I've tried last 3 or 4 commits and no difference. Is it a bug?
-
@d-healey Ok, now I change the path of Xcode and export finally started. But, I've got these errors now:
What does it mean?
-
@nouslou That could be a bug in HISE... @Christoph-Hart ?
-
@d-healey I tried different combinations of Xcode and hise versions and with no results (( This screenshot is from Xcode 13 and todays commit of new_layout branch. What it can be? I tried also Xcode 12, 12.2, 12.5 + 5-6 different commits from new_layout branch, developer branch and even master branch. All that Hise versions were compiled without issues, but I'm not able to export plugin. Every time the same error.
-
It tells you in the error message. The architecture in the project's .jucer file is set to arm64 and you're trying to include the IPP which only works on x86.
-
@d-healey But I disable un-needed architectures.
-
@nouslou Is that your project's .jucer file or HISE's .jucer file?
-
@d-healey This is Projucer which is in the Hise folder directory from GitHub. I choose x86_64 before compilation Hise on my computer. And after compiling - I just open Hise, open my test project and trying to export vst
-
@nouslou When you export from HISE it creates a .jucer file for your project in the Binaries folder.
-
@d-healey Oh, I opened AutogeneratedProject.jucer in my project and there is:
But why? if I didn't choose it before building Hise. How to fix this?
-
@nouslou said in Develop branch build status:
But why?
Because that is the default settings.
if I didn't choose it before building Hise
It's not related to the settings you chose when building HISE.
How to fix this?
Uncheck the boxes and resave the file.
-
@d-healey if I will resave it - does it mean that I can not to delete Binaries folder? On my old Mac I usually did this when I re-exported instruments
-
@nouslou You can delete it if you want, but when it's time to reexport you'll need to edit the jucer file again - but I think you'll need to do this anyway because it's regenerated by HISE.
-
@d-healey tried several times to resave that file, than export --->> same errors, and after opening that .jucer file again - arm64 and arm64e enabled again. What am I doing wrong now?
-
@nouslou No don't go to export after you save it, that will overwrite it. Just do the same as when you compile HISE, File >> Save and open in IDE.
-
@d-healey you mean now I need to export plugin directly from Xcode? Product - Build for - Profiling?
-
Yes. That is what HISE does when you click export, only it uses the commandline tools. You can also use the command line by running the script file that HISE created in the Binaries folder.
-
@d-healey David, thank you very much! Will try it !
-
still impossible to compile hise with xcode 12.2 and bigsur 11.5.2 I had managed to compile with xcode 12.5 but could not compile a vst. I tried the new layout, scriptnode, devloper branches .. none of them want to work. a lot of errors that I cannot list here. what is the configuration that works for intel bigsur please?