Develop branch build status

[d.healey]

@nouslou Is that your project's .jucer file or HISE's .jucer file?

[nouslou]

@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

[d.healey]

@nouslou When you export from HISE it creates a .jucer file for your project in the Binaries folder.

[nouslou]

@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?

[d.healey]

@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.

[nouslou]

@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

[d.healey]

@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.

[nouslou]

@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?

[d.healey]

@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.

[nouslou]

@d-healey you mean now I need to export plugin directly from Xcode? Product - Build for - Profiling?

[d.healey]

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.

[nouslou]

@d-healey David, thank you very much! Will try it !

[yall]

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?

[d.healey]

@yall

Use the new_layout branch and XCode 13.

[yall]

@d-healey as I write to you. hise has just been compiled and a vst is also being compiled. I didn’t touch anything. very weird. by dint of forcing things apple had had enough of me ^^

[d.healey]

FYI Christoph merged new_layout into develop today.

[DanH]

@d-healey Have you built it yet? I'm getting lots of RLottie complaints even though I thought I'd set it all to disabled i Projucer...

[d.healey]

@danh I built it yesterday, but there have been more commits today that might cause build issues. I know Christoph is planning to integrate rlottie directly into the source code so we don't need to ship separate DLLs so I think the errors you are seeing might be related to that.

This is the commit I've built - 3aa3dcfd9882e489de41db346b4b2c0caad163c4

[crd]

@d-healey That is great news. I was hoping that would happen.

[d.healey]

@danh I just tested and it's possible (on my system at least) to build the latest commit if you disable rlottie in projucer.