It seems that with VST SDK 3.6.12 (or some earlier revisions) folder layout and filenames have changed, so that
In file included from [..]/JuceLibraryCode/include_juce_audio_plugin_client_VST2.cpp:9:
In file included from ../../../sdk/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST2.cpp:27:
../../../sdk/juce/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:95:10: fatal error: 'pluginterfaces/vst2.x/aeffect.h' file not found
#include "pluginterfaces/vst2.x/aeffect.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
In the VST2 section of the VST SDK there are following files:
aeffeditor.h
audioeffect.cpp
audioeffect.h
audioeffectx.cpp
audioeffectx.h
vstplugmain.cpp
What to do? Which VST SDK version should I use with latest JUCE release? Where do I get previous VST SDK versions from (if needed)?
No, you’re not doing anything stupid. I thought that when you went into one of the submodules you would be able to jump back in history to find the VST2 SDK, but it’s VST3 only.
Do you have a VST2 license with Steinberg? If you don’t you won’t need the SDK, and if you do you probably have an older copy of the SDK somewhere already.
We need a VST2 license to be able to distribute the SDK and/or any plugin built with it. But if we just want to build a VST2 plugin for ourselves, or make a VST2 host, we still need to get the VST2 SDK, without needing any license.
Ah, thanks,
so the VST2 SDK can be viewed at independently from VST3. So a reasonable combination of a current VST3 SDK and the latest VST2 SDK should do it…!?
There’s a VST3 SDK distributed with JUCE (we have a special agreement with Steinberg that allows us to distribute the VST3 SDK), so you only need the VST2 SDK.
Btw/fyi: in my yesterdays JUCE workshop with 3.6.12 and JUCE 5.4.1 it was impossible to create VST3 plug-ins, we had to go back to 3.6.11 and everything worked as expected. macOS and windows.
Unfortunately, some of these links don’t seem to work anymore.