I’m trying to generate a VST3 plug-in with no success. I would appreciate if someone could help me, or at least tell me if there is any known issue. Below are the details:
Code::Blocks (Windows) with the x86_64-w64-mingw32-g++ compiler
Projucer normally generates a VST project. After some minor tweaks, Code::Blocks correctly generates a .lib library, a working executable and a VST2 dll file.
However, no matter how you change the settings in Projucer (“Build VST3” enabled, “Build Audio Unit” enabled etc…), Code::Blocks always builds the same .exe with the VST2 dll stuff.
I inspected the Code::Blocks project file (.cbp) and I can see the following flags being generated:
-DJucePlugin_Build_VST=1 -DJucePlugin_Build_VST3=0 -DJucePlugin_Build_AU=0 -DJucePlugin_Build_AUv3=0
no matter what the settings are in Projucer.
Of course, I correctly set the global paths, including
VST3 SDK: D:\dev\juce\VST_SDK\VST3_SDK
where the Steinberg SDK was downloaded. Note that the Code::Blocks project file (.cbp) generated by Projucer does not even contain this string at all.
I desperately tried to hack the Code::Blocks project by forcing something like:
… -DJucePlugin_Build_VST3=1 …
… -ID:\dev\juce\VST_SDK\VST3_SDK …
which are actually used (I can see that in the message log), but nothing changes, and the compiler keeps on taking a file named “include_juce_audio_plugin_client_VST2.cpp” instead of its VST3 counterpart. Of course, hacking the compilation manually is not a great idea.
The problem is simply that the VST3 toolflow in Projucer doesn’t seem to work at all, as if the settings were completely ignored while generating the Code::Blocks project (btw, experimenting with the Exporters, I noticed that the same happens with the Linux Makefile).
Any hint is absolutely welcome!!