Scriptnode DSP Compilation help (again!)

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

[DanH]

@ustk gotcha, so can I log into XCode with my developer credentials?

[Christoph Hart]

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

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

It expects the ID, not the email (something like PF98FSFGASFE). Entering the email here might cause weird issues.

[DanH]

@christoph-hart oh yes, doh!

[DanH]

@christoph-hart Entered the right info, same result... Can't figure it out :crying_face:

[DanH]

@christoph-hart FYI - Having compiled the .dll I rolled back to a recent commit of HISE which lets me build a standalone instrument. With the .dll in the project I can't open the Standalone - it's a straight crash on OSX. Without the .dll in the project it's ok.

On Windows I built the latest Develop and built a Standalone from the project with the .dll. Again it won't open, crashes before anything happens, nothing opens etc. Agai without the .dll it's fine.

Have tried au and vst3 too...

[DanH]

@Christoph-Hart Made a simple project with only a SinWaveGen plus a Script FX with the .dll loaded in and I still get an instant crash.

Are people exporting their plugins with .dlls in them ok?

[crd]

@danh

I’ll make a simple test project tomorrow to try and let you know. I have many many issues making the dlls that I have been waiting for some free time to properly report to the GitHub issues page Christoph made.