Version 7.0.0
- Migrated Jamba to use VST3 SDK 3.7.8 (release notes). Please check other release notes to see what has changed since 3.7.5 (last Jamba supported version).
- As explained in issue #16, Jamba is no longer supporting VST2
- Added a way to patch the SDK by defining the CMake cache string
JAMBA_VST3SDK_PATCH_DIR
(Jamba uses it on Windows/DLL build to fix an issue withwin32resourcestream.cpp
, but you can also use it for your own purposes): by defining this variable, 2 things happen- Jamba copies the SDK inside the build folder
- Jamba copies all the files under
${JAMBA_VST3SDK_PATCH_DIR}
on top of this copy while never modifying a local version of the SDK
Migration suggested
Remove the
option(JAMBA_ENABLE_VST2 "Use VST2" ON)
entry from yourCMakeLists.txt
(and you can clean up any references to vst2 if you want to).Note that if you do not remove it (or set it to
OFF
), anyvst2_sources
will try to get compiled and this will no longer work