Develop branch build status

[yall]

@d-healey I come back to you regarding the compilation of hise 5 hours later;)
I managed to compile hise with my following config.
xcode 12.5.1
development target 14.

I also put in projucer, in the mac os part, on native architecture of build machine. (they were on 64 bits)
.
big on 15.5.2 last develop version

now do you think the audio units will work in Logi pro?
because so far I still have not had an answer on this subject (logic belongs to apple so rosetta will not work)

[d.healey]

@yall said in Develop branch build status:

logic belongs to apple so rosetta will not work

According to Apple it should work

If you're using an Audio Unit plug-in that wasn't built for Apple silicon, Logic Pro or Final Cut Pro recognizes the plug-in only when Rosetta has been installed.

If you're having issues with this you should make a new thread so we can keep track of the problem.

[Lindon]

@yall said in Develop branch build status:

@d-healey I come back to you regarding the compilation of hise 5 hours later;)
I managed to compile hise with my following config.
xcode 12.5.1
development target 14.

I also put in projucer, in the mac os part, on native architecture of build machine. (they were on 64 bits)
.
big on 15.5.2 last develop version

now do you think the audio units will work in Logi pro?
because so far I still have not had an answer on this subject (logic belongs to apple so rosetta will not work)

try running auval for a start...

[yall]

@Lindon
can you tell me what AUVAL is? I don't know at all please

[Dan Korneff]

@yall https://auval.ca/

[d.healey]

@yall https://developer.apple.com/library/archive/documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/AudioUnitDevelopmentFundamentals/AudioUnitDevelopmentFundamentals.html

[Lindon]

@dustbro said in Develop branch build status:

@yall https://auval.ca/

LOL...

[Lindon]

@yall said in Develop branch build status:

@Lindon
can you tell me what AUVAL is? I don't know at all please

check Daves URL above, you need the section called:

Audio Unit Validation and Testing in the menu(on the left) item Audio Unit Development Fundamentals

its not that clear(typical Apple) what you do but compile your AU plug-in and put it in the folder:

Completer/Library...etc.. folder

open a terminal window and type this:

auval -h

to get a list of all the command options.

The commands you want to use are:

auval -a

(to list and get your AU's recognised type , plugin code and company code

then auval -v (with those details from above)

it will run a series of tests (the ones LOGIC uses) to validate the plugin - if this succeeds then LOGIC will at least not reject your plug-in on validation grounds...

[A Former User]

@LinuxVst @d-healey Coming back to your earlier remarks about compiling HISE on Big Sur... I have now tried Xcode 12.4, 12.5, 12.51 and 13 without any success yet. I've set the macOS deployment target to 10.14 as suggested, but I always hit similar issues.

Has anybody been successfully building HISE and compiling plugins on macOS Big Sur yet???

[Dan Korneff]

@UrsBollhalder I had to downgrade to Xcode 12.0 to make it work. I haven't tried 12.2 yet, which would allow the export of native M1 plugs.
My be my project for this week since people really want native M1 plugs.

[A Former User]

@dustbro True! Maybe I'll try 12.2 quickly... ALthough quickly doesn't exist when it comes to downloading and unpacking XCode!!!

[d.healey]

@UrsBollhalder Let me know how you get on, I need to do some compiling on MacOS soon.

[A Former User]

@d-healey Well, so far no luck... 12.2 didn't resolve the issue... I'll keep you posted.

[d.healey]

Success with Xcode 13 - will probably work with 12x too.

I just had to disable un-needed architectures.

[A Former User]

@d-healey said in Develop branch build status:

Success with Xcode 13 - will probably work with 12x too.

I just had to disable un-needed architectures.

I'll try that right now... I've been at it for 2 days now... losing my shit... unable to get a working compile on Big Sur!

I get a bunch of these now... I believe to know that these are vst sdk-related but I don't know where to fix it! I think the sdk-path is not set correctly... but where!??!!

[d.healey]

Nothing to do with the SDK, that only comes into play when exporting plugins. This error is because Christoph removed the STK nodes from script node but you still have the modules in your .jucer file. You need to remove it or use the .jucer file from github.

[A Former User]

@d-healey Ok... I just removed that module... But I still get a shitload of those Reference to 'Point' is ambiguous - errors... Any ideas? I'm on XCode 13 now...

I have:

• deployment target set to 10.14
• disabled all unwanted architectures
• IPP installed and path-fixed on my HD
• also tried with the deprecated legacy build system

BUT... I somehow was trying to compile the master branch... Very mysterious... trying again now...

[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