sudara / pamplejuce

A JUCE audio plugin template. JUCE 8, Catch2, Pluginval, macOS notarization, Azure Trusted Signing, Github Actions
https://melatonin.dev/manuals/pamplejuce
MIT License
429 stars 43 forks source link

Debug VST in AudioPluginHost #99

Open hushaudio opened 5 months ago

hushaudio commented 5 months ago

Is it possible to debug a VST in the AudioPluginHost or a DAW?

I have an issue that requires me to debug my plugin as a vst but I cannot debug as a vst with the template as is, only as a StandAlone app.

I could create a new projucer project and do it the oldschool way but I'd like to be able to stay in pamplejuce to simplify things and avoid having to copy/paste adjusted code to the pamplejuce project, etc.

Any helpful leads on how to accomplish this would be much appreciated!

sudara commented 5 months ago

Is it possible to debug a VST in the AudioPluginHost or a DAW?

Definitely! I use the AudioPluginHost daily.

The setup will depend on your IDE. Once you have the AudioPluginHost built, you should be able to select the executable you want to start up after build in your "scheme" or "configuration" (different IDEs use different terminology here).

In Xcode, be sure to check "Debug Executable" Arc - 2024-06-05 32@2x

DAWs can be slightly more tricky...

hushaudio commented 5 months ago

Ah yes, I use xcode for debugging usually, but I am using the cmake builds. Does pamplejuce create an xcode project or does that need to be done manually?

hushaudio commented 5 months ago

ah, found the way -> cmake -G Xcode ., though im getting an error when I try build it test_plugin/<command line>:64:9 'JUCE_WEB_BROWSER' macro redefined

sudara commented 5 months ago

oh were you just using cmake to build the binaries before? Interesting...

not sure re: the macro... maybe make sure you clean the build folder if you are switching generators to Xcode (or use a different build folder)