Log In
Register
Home
Topic RSS
Hi,
I've followed the video/book instructions and I'm stuck in cMake trying to build my first project (windows 10). That's what I'm getting:
CMake error at cmake/vst_cmake/CMakeLists.txt : include could not find requested file:
SMTG_Global
And it happens to every reference to SMTG files.
Could you help me?
Thanks
Which version of the VST3 SDK are you using?
Steinberg just updated it and changed some stuff as usual, so it broke some of my CMake modules.
You should use VST3 SDK 3.7.1 which is the currently supported version (see the Download page as well).
I am not able to legally post the SDK but you can usually find one out there on the internet. So, please first make sure you have the correct VST3 SDK. Steinberg used to keep a legacy folder with old SDKs but they seem to change things around often so I am not sure if they still have that repository.
I will not have time to revise the ASPiK SDK for the new VST3 SDK until sometime after April 30 (this is because the semester is ending at the University of Miami and we have exams, etc...). However this is on my current TODO list because they broke some of my existing code during the revision process.
Will
Thanks, Will !
I'm using VST3 SDK 3.7.1 . In fact I just found a solution. The problem is with CMake finding the cmake/modules folder. I moved all the stuff inside the VST3_SDK to one level up - VST_SDK and it worked. Ok, that's not the most elegant solution, and it could be a problem for another system that tries to use the SDK, but it worked. Maybe if you change the cmakelist a little it will run ok.
I've found another problema when building the "do nothing" plugin: it is in plugingui.h - const PlatformType& platformType = kDefaultNative, the error is "kdefaultNative: undeclared identifier".
But ok, I'm offtopic now. Will work more and try to find what the problem is.
Thanks, man!!
I think you are probably one directory layer off because of the way the projects are packaged on this site.
If you download any of the projects, the project folder will be inside of an outer containing folder. For the RackAFX projects, the outer folder is RAFX7 and for ASPiK, it is called ASPiK. If this is the case, you need to go into that outer folder and move the "real" project folder up one directory hierarchy. Then, you can discard the RAFX7 or ASPiK folder.
Will
Actually I think the problem is in CMake's VST SDK Location: ${SDK_ROOT} - It expects the SDK_ROOT to be VST_SDK but after install, everything is in a subfolder named VST3_SDK instead. It must be a case of changing something in the CMake scripts , but copying all the stuff inside VST3_SDK to VST_SDK solved the problem.
Offline
Hi fabhenr,
Have you edited the CMakeLists.txt file? Are you doing a universal build? If your projects are in ALL_SDK/myprojects, you need to make sure set(UNIVERSAL_SDK_BUILD TRUE) even if you are only building the plug-in for VST. You would set set(AAX_SDK_BUILD FALSE), set(AU_SDK_BUILD FALSE), and set(VST_SDK_BUILD TRUE). If you are not building a universal project then you would set(UNIVERSAL_SDK_BUILD FALSE) as well as set(AAX_SDK_BUILD FALSE), set(AU_SDK_BUILD FALSE), and set(VST_SDK_BUILD TRUE). In the latter case, I believe the myprojects folder would reside in the VST_SDK folder. Just a thought.
Tim C
Offline
fabhenr said
Thanks, Will !I'm using VST3 SDK 3.7.1 . In fact I just found a solution. The problem is with CMake finding the cmake/modules folder. I moved all the stuff inside the VST3_SDK to one level up - VST_SDK and it worked. Ok, that's not the most elegant solution, and it could be a problem for another system that tries to use the SDK, but it worked. Maybe if you change the cmakelist a little it will run ok.
I've found another problema when building the "do nothing" plugin: it is in plugingui.h - const PlatformType& platformType = kDefaultNative, the error is "kdefaultNative: undeclared identifier".
But ok, I'm offtopic now. Will work more and try to find what the problem is.
Thanks, man!!
I changed line 451 of plugingui.h to
const PlatformType& platformType = PlatformType::kDefaultNative,
and this seemed to resolve this issue (Visual Studio 2019 made this suggestion). The IIRFilters project is now building successfully in VS 2019.
Line 1887 of vst3plugin.cpp (in the vst_source subdirectory) also needs to be changed from:
VSTGUI::PlatformType platformType = VSTGUI::kDefaultNative;
to
VSTGUI::PlatformType platformType = VSTGUI::PlatformType::kDefaultNative;
This applies to VST 3 SDK Version 3.7.2, ASPiK version 1.6.7
ASPiK 1.6.7 does not support VST3SDK 3.7.2 (see the release notes and website).
I am working on ASPiK 1.6.8 right now that includes 3.7.2 support.
Note that there are other issues than this, and the upcoming release will address these, as well as update VST3 specifically for SynthLab. There are changes to CMake (from Steinberg, not me) as well that break the MacOS VST3 plugin setup.
You should only use VST3SDK 3.7.1 with the current release. Let me know if you need a copy as Steinberg deletes them on each new release...
Will
Offline
Hi Will,
As you suspected, I've been unable to find a copy of the VST 3 SDK v3.7.1, however, I'm still only working my way through Chapter 6 "ASPiK Programmming Guide", typing the code into my generated IIRFilters project.
Given the fact that I still have a sizeable chunk of the book to read before I get to Chapter 11, when the programming begins in earnest, is it worth waiting for ASPiK 1.6.8, or would you advise I downgrade my VST 3 SDK to 3.7.1 right away? If so, I will need a copy. Thanks.
You can get a copy of VST3 SDK 3.7.1 here:
https://willpirkle.com/special/VST_SDK.371.zip
It should only be about a week (fingers crossed) before the next release so that is up to you. If you have the disc space, just keep both SDKs for now - I usually have at least two VST3 SDKs "alive" for testing - the current release and the previous one. Sometimes there are just too many changes to work on with just notes...
Will
Offline
W Pirkle said
You can get a copy of VST3 SDK 3.7.1 here:https://willpirkle.com/special/VST_SDK.371.zip
It should only be about a week (fingers crossed) before the next release so that is up to you. If you have the disc space, just keep both SDKs for now - I usually have at least two VST3 SDKs "alive" for testing - the current release and the previous one. Sometimes there are just too many changes to work on with just notes...
Will
Thanks Will.
Most Users Ever Online: 152
Currently Online:
5 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Chaes: 56
jim: 53
Skyler: 48
Derek: 46
Frodson: 45
Peter: 43
TheSmile: 43
clau_ste: 39
Nickolai: 39
JimmyM: 33
Member Stats:
Guest Posters: 1
Members: 732
Moderators: 1
Admins: 5
Forum Stats:
Groups: 13
Forums: 42
Topics: 804
Posts: 3087
Moderators: W Pirkle: 640
