Develop branch build status

[d.healey]

@UrsBollhalder said in Develop branch build status:

I somehow was trying to compile the master branch.

How many copies of the HISE source code do you have on your system? ;)

[A Former User]

@d-healey ONE!!! I set up a clone and pull directly from Christoph's repo! As you instructed me master Jedi!

But I have a working backup on an external drive though... but just for emergencies.

And also...

[A Former User]

@UrsBollhalder So in hindsight... Big Sur, XCode 13, new_layout branch

• XCode 13 and Command Line Tools for XCode 13 installed (https://developer.apple.com)

• deployment target set to 10.14 (you can and probably should do this in multiple places => projucer and XCode)

• disable all unwanted architectures (as posted by @d-healey above)

• IPP installed and path-fixed on my HD (@LinuxVst has a great post about this, more or less up on top in this thread)

• I ran into problems a couple of times when XCode doesn't have full disk access => macOS system preferences

[A Former User]

@d-healey Have you tried to compile a plugin yet?

[d.healey]

@UrsBollhalder Yes, worked fine, VST3 on all three operating systems and AU on Mac.

[A Former User]

@d-healey Hmm... Directly from HISE or did you have to tinker the Xcode file before? I only could export a debug version from Xcode, but not a release! Also, what is the process for vst3 export?

[d.healey]

@UrsBollhalder said in Develop branch build status:

Directly from HISE

Yes, I might have tweaked something in the .jucer file, can't remember, but didn't change anything in xcode.

what is the process for vst3 export?

Check the vst3 box in project preference before export.

[A Former User]

@d-healey said in Develop branch build status:

Check the vst3 box in project preference before export.

Do I need a special sdk in the HISE folder for that?

[d.healey]

@UrsBollhalder It's included with JUCE so you don't need to do anything.

[A Former User]

@d-healey I get these:

Any idea what the problem could be? Why is it building for arm-64?

[d.healey]

@UrsBollhalder Looks to be IPP related, I don't have IPP installed. Try exporting with IPP disabled.

[A Former User]

@d-healey It was disabled actually when this happended... Now I checked IPP again, but same result...

[d.healey]

@UrsBollhalder said in Develop branch build status:

It was disabled actually when this happended...

Open the .jucer file and see if there is anything suspicious there

[A Former User]

@d-healey You mean the AutogenerateProject.jucer, I suppose?

[d.healey]

@UrsBollhalder Yeah

[A Former User]

@d-healey In there it builds for arm processors... I know unchecked those, saved and opened it up in Xcode. Do you from here on build (Command-B), or build for profiling, or for running?

[d.healey]

@UrsBollhalder Build for profiling for a release build.

[A Former User]

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

[A Former User]

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

[d.healey]

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