<![CDATA[Linker error when using JUCE classes in third party node template]]>Dear HISE community,

related to my first post, I have a couple more issues that I could use your help for.

I wanted to integrate a JUCE effect for which I have the c++ source code in the form of AudioProcessor.h/.cpp.
This code compiles and works with JUCE 7 and 8.

Question 1. Will HISE be bumped to a more recent version of JUCE at some point?

For now, I created a backport for JUCE 6.

To integrate it into HISE, I followed the described procedure:

  1. Tools -> Create C++ third party node template
  2. I copied the AudioProcessor.cpp/.h file into the src/ subdirectory.
  3. I wrote glue code to actually use the code in the generated template.
  4. I included both AudioProcessor.cpp and AudioProcessor.h in the template file.
  5. I compile the code using Export -> Compile DSP networks as dll

Now the compilation works well, however the linking fails, indicating that code from juce::AudioProcessor has not been linked.
More precisely, no code seems to have been compiled for arm64 (I'm compiling a MacBook with Intel hardware, using XCode and MacOS Ventura).
Some other classes from JUCE compile and link without any problems.

When I actually copy the definitions of the missing functions from JUCE (that comes with HISE) into the third party node template, the linker errors vanish.
(Please note, that I did not remove all linker errors since I do not consider that a solution to the problem, I just wanted to check if the deinitions are actually missing).

Question 2. So I assume that the source files (at least containing juce::AudioProcessor) are not linked properly in the export sequence of HISE?

The last question assumes that some node with dials has been added to the DSP network.
Please also assume that HISE has beed compiled as VST3 plugin and is used in a DAW (I'm using FL Studio).

Question 3: Is there a way to automate dials/sliders/... of HISE in the DAW? Again related to my first post, I wish to test the effect I'm designing right inside the DAW. (Afterall I assume that is the intended use-case of the plugin-version of HISE?)

Thank you very much in advance!

]]>https://forum.hise.audio/topic/10164/linker-error-when-using-juce-classes-in-third-party-node-templateRSS for NodeSat, 11 Jul 2026 04:47:57 GMTTue, 30 Jul 2024 13:27:02 GMT60<![CDATA[Reply to Linker error when using JUCE classes in third party node template on Thu, 08 Aug 2024 09:11:49 GMT]]>Found the file: hi_backend/backend/ProjectDllTemplate.cpp

]]>https://forum.hise.audio/post/84463https://forum.hise.audio/post/84463Thu, 08 Aug 2024 09:11:49 GMT<![CDATA[Reply to Linker error when using JUCE classes in third party node template on Tue, 06 Aug 2024 12:26:12 GMT]]>Update:

I tested the same workflow on Windows and encoutered the same problem (linker errors). This made me investigate a little more and I found the reasons for the linker error:

  1. I have another installation of JUCE (v. 8.0.0) that may have overriden the module paths. I had to make sure that the module is set to the version shipped with HISE.
  2. The AutogeneratedProject.jucer that is generated does not include the "juce_audio_processors" module. Add it and it works, on both mac and Windows.

I don't know why this choice was made and if there is a way in the UI of HISE to change which modules are included in the auto generated project.
Alternatively, if someone could point me to where I have to modify the source code of HISE would great! Maybe that is quickly done by @Christoph-Hart ?

Otherwise, exporting the plugin using the HISE interface will overwrite the project each time and I have to add the module again and again.

]]>https://forum.hise.audio/post/84375https://forum.hise.audio/post/84375Tue, 06 Aug 2024 12:26:12 GMT<![CDATA[Reply to Linker error when using JUCE classes in third party node template on Thu, 01 Aug 2024 17:50:32 GMT]]>I might share a few more insights, maybe someone has an idea.

First, find an image of the aforementioned linker error below.

Screenshot 2024-08-01 at 19.13.47.png

I assume that if I would compile the same thing on Apple Silicon, I would get a x86_x64 linking error.

Interestingly enough, when I export the HISE project containing the very same code as FX plugin (using the export functionality in HISE), I do not get linker errors.

Any idea?

]]>https://forum.hise.audio/post/84085https://forum.hise.audio/post/84085Thu, 01 Aug 2024 17:50:32 GMT