Scriptnode DSP Compilation help (again!)

[DanH]

I feel like something obvious is missing from my project / HISE.

• I've compiled the latest Develop (I've tried all this in workbench too btw)
• I've made a completely new DSP network within HISE as a Chorus effect, all works, sounds good.
• I've wrapped it all into a DSP network
• I've pressed 'P' and "Allowed Compilation" of the network.
• I've gone to Export, 'Compile DSP networks as dll'
• It begins compiling, and then I get a load of errors. So many it hits its limit!

It seems to have a problem with absolutely everything in the network which is why I think there's something missing in the project, in HISE, or something I haven't generated.

example of some of the errors below:

❌  /Users/DanH/CHORUS TEST/DspNetworks/Binaries/Source/CHORUS.h:25:41: use of class template 'jdsp::jpanner' requires template arguments

                                  jdsp::jpanner, 

❌  /Users/DanH/CHORUS TEST/DspNetworks/Binaries/Source/CHORUS.h:43:48: use of undeclared identifier 'chain2_t'

                                  wrap::fix<2, chain2_t<NV>>, 

❌  /Users/DanH/CHORUS TEST/DspNetworks/Binaries/Source/CHORUS.h:44:48: expected a type

                                  chain3_t<NV>>;

[DanH]

@danh is this at all obvious to you @Christoph-Hart ?

[ustk]

@danh Can you export a very simple DSP? like an empty one (if ever there's no check for that) or with just a Math.mul or something simple...

[DanH]

@ustk yes

[Christoph Hart]

@danh The code generator is still a bit rough around the edges, but that's why I've created the scriptnode testsuite repository.

https://github.com/christophhart/scriptnode_testsuite/issues

Please submit this example (exported as snippet) as an issue, then I'll add a test case and make sure it compiles.

[DanH]

@christoph-hart Thanks have done that (message is from DHPlugs...)

I did also try to make from scratch is a fresh project but the same errors happened.

Thanks for the help - When will I know if/when you've had a look? On GitHub?

[DanH]

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

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?