Scriptnode DSP Compilation help (again!)

[DanH]

@christoph-hart It's compiled! Thankyou Thankyou Thankyou!! :folded_hands:

PS - When I try to compile the plugin I'm still getting the Ad Hoc error below:

❌  error: Ad Hoc code signing is not compatible with the Hardened Runtime. Sign with a Mac Developer certificate or disable the Hardened Runtime by setting the ENABLE_HARDENED_RUNTIME build setting to NO. (in target 'HALO - App')

[d.healey]

@danh That error is pretty clear. You're trying to code sign from xcode by the look of it and you have hardened run time enabled.

[DanH]

@d-healey Weird though because I've not done anything different, just built latest Develop and this suddenly appears. If I roll back a couple of commits it's fine... I've no idea how to turn the Hardened thing off either

[Christoph Hart]

[DanH]

@christoph-hart Thanks!

[DanH]

@christoph-hart So this was Disabled by default. I built again with it set to Disabled, and the same has happened. I switched it to on and I couldn't even build HISE in XCode. Am I the only one with this error?

[d.healey]

@danh Are you saying this is enabled in your project's .jucer file or in the HISE .jucer file? or both?

[DanH]

@d-healey both... although in the project it was enabled, and re-enabled itself even after I switched it off

[DanH]

@d-healey @Christoph-Hart when I hit compile in HISE it seems to switch my project's Hardened Runtime setting to enabled again....

[d.healey]

@danh said in Scriptnode DSP Compilation help (again!):

when I hit compile in HISE it seems to switch my project's Hardened Runtime setting to enabled again....

There is no "compile" in HISE ;) When you export from HISE it generates a new .jucer file, so that will overwrite any changes you made to the one you edited.

[DanH]

@d-healey sorry, yes exactly. I wonder why it's decided to flip that setting off from the default setting to enabled all of a sudden

[ustk]

@danh seems that I always have it enabled, using the last Hise version and an older one (about 3 weeks older)
The Jucer info says it is required for app notarization, so "enabled" seems to be the right default setting

[DanH]

@ustk Thanks, are you able to export a plugin from HISE?

[d.healey]

If enabled is the correct setting then the other half of the error message is the problem, ad-hoc signing. Are you code signing through xcode?

[DanH]

@d-healey I'm not trying to codesign at all. I do all that separately in terminal. I've changed nothing in Xcode, my project etc except using latest develop

[d.healey]

@danh Have you put anything in here?

[DanH]

@d-healey nope, just filled it in with my email as per my dev account with Apple. Saved, restarted, same error.

[DanH]

@d-healey So can HISE codesign for you when exporting?

[d.healey]

@danh No, but I assume xcode can based on that setting in the HISE preferences - I've never tried it. You'd still have to notarize it yourself.

[ustk]

@danh Hise has nothing to codesign, it is not Hise's job to build and codesigning happens on a built binary. Hise just passes the info to XCode.