Develop branch build status
- 
 @d-healey Ok... Because now, when hitting command-B, it just compiled a debug version again... I'll try build for profiling! 
 Did you get a working arm-build btw? Because that would be the goal of this adventure....
- 
 @d-healey Ah... I got a build. But know openGL left the building without saying goodbye... And why is there no place in the audio settings menu where I can switch that bugger on now?? How do you guys do it? I mean mentally? Bleeding eyeballs again here...   EDIT: HISE_USE_OPENGL_FOR_PLUGIN=1 was my friend... 
 I would want it to compile with openGL set to true by default... but at least I got it working again...
- 
 @UrsBollhalder said in Develop branch build status: Did you get a working arm-build btw? A couple of years ago I did - search the forum and you'll find my struggles :p I would want it to compile with openGL set to true by default... Project preferences extra definitions. 
- 
 @d-healey ffs. Sticking on Mojave for a while lol  Who's with me?! Who's with me?!
- 
 @DanH  macOS is no stroll in the park... yep macOS is no stroll in the park... yep
- 
 It looks like the Custom Settings floating tile doesn't follow Component Colors in the Property Editor. Using Develop and New Layout branch. MacOS 11.6 
 Does anyone know a workaround?
 I would just use the new settings API, but OpenGL isn't available in there yet. @Christoph-Hart Will this eventually be available?Also just noticed that clicking the Rebuild Interface button on the Canvas doesn't redraw my panels, but hitting F5 does? 
- 
 
- 
 @d-healey  
- 
 Hi, guys! Can you, please, advise me what is the most stable and good working combination of XCode and Hise version? Need to be able to export vst's for native M1 too. I have macbook pro on M1 chip, Big Sur (11.4). Thank you! 
- 
 Ok. Installed Xcode 12.0 and Hise from the develop branch, Installed IPP and got this error while compiling:  How can I solve this? 
- 
 @nouslou IPP is only for Intel systems. 
- 
 @d-healey So all I need is uncheck the IPP in projucer? I use conv. reverbs in my plugins. Will this somehow affect the performance of the plugins themselves for users with intel computers? 
- 
 If exporting as a universal binary, then why not keeping IPP? so M1 won't use it while intel will, no? 
- 
 @nouslou said in Develop branch build status: so all I need is uncheck the IPP in projucer? You'd need to remove the paths in Project as well. Also you should use XCode 13 I think. 
- 
 @d-healey In that case will exported plugins work fine on intel machines? I mean if I will not use IPP. Or is there any solution to fix this without deleting IPP? 
- 
 @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.  




