CMake Error at cmake/vst_cmake/CMakeLists.txt:60 (smtg_get_default_vst3_path): | CMake and ASPiK Help | Forum


Please consider registering

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —

— Match —

— Forum Options —

Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
CMake Error at cmake/vst_cmake/CMakeLists.txt:60 (smtg_get_default_vst3_path):
November 10, 2021 - 12:17 pm
Member Since: November 10, 2021
Forum Posts: 10
sp_UserOfflineSmall Offline

Hi, First of all I am going to say the versions that I am using of each program:

- Cmake 3.22.0

- VST3 SDK 3.7.3

- AAX_SDK 2.3.2


- Visual Studio 2019

- ASPIK 1.7.2

I'm following the ASPiK video tutorials but I can't generate the first plugin project with cmake and making use of universal myprojects folder (Using only VST if I get it). Attached the error that I get in cmake:

Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22000.

--- Updated File: project_source/source/PluginKernel/plugindescription.h


------> Starting AAX Project Build:

AAX SDK Location: C:/Users/David/Documents/ALL_SDK/AAX_SDK


-> Adding AAX ported project in source folder: C:/Users/David/Documents/ALL_SDK/project_source

AAX Target Name: VolumePluginl_AAX


------> Starting VST Project Build:

VST SDK Location: C:/Users/David/Documents/ALL_SDK/VST_SDK/VST3_SDK


[SMTG] SMTG_PLUGIN_TARGET_PATH is set to: C:/Program Files/Common Files/VST3

-> Adding VST ported project...

VST Target Name: VolumePluginl_VST


[SMTG] Setup running validator for VolumePluginl_VST


VSTGUI will use the embedded Expat package!

Configuring done

CMake Error at project_source/cmake/aax_cmake/CMakeLists.txt:162 (add_library):
Cannot find source file:


Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .h
.hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc

CMake Error at project_source/cmake/aax_cmake/CMakeLists.txt:162 (add_library):
No SOURCES given to target: VolumePluginl_AAX

November 10, 2021 - 1:06 pm
Member Since: January 29, 2017
Forum Posts: 689
sp_UserOfflineSmall Offline

For AAX, you must pre-compile the libraries so they are available when you create the project.

See the ASPiK docs here:

This is an AAX issue, not ASPiK. 

For VST3 pre SDK3.6 (that I recall) it was similar in that the base objects had to be pre-compiled. For the new VST3 projects, you will see that the VST3 Visual Studio (and XCode) solutions are gigantic as you must re-build all necessary libraries for each and every plugin project. So, that is the trade off.

If you have not built the AAX sample projects (which appears to be true) then I would suggest building at least one of them (maybe the Volume plugin) to make sure your SDK is good.

For VST3 I also build all the samples each time a new SDK comes out to make sure there are no issues. If you can't build the sample projects successfully (due to directory structures, corrupt files, compiler settings, etc...) then you won't be able to build the ASPiK (or JUCE, or iPlug2, etc...) either. 


November 10, 2021 - 1:34 pm
Member Since: November 10, 2021
Forum Posts: 10
sp_UserOfflineSmall Offline

I am having problems compiling the AAX libraries, can I follow the plugin development described on the web and in the book using ASPiK and RackAFX only with VST?

My goal is to make a plugin as an autotune for my final degree project (I am a Telecommunications engineering student specialized in DSP)

Forum Timezone: America/New_York

Most Users Ever Online: 152

Currently Online:
5 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Chaes: 56

Skyler: 48

StevieD: 46

Derek: 46

Frodson: 45

Peter: 43

TheSmile: 43

Nickolai: 43

clau_ste: 39

jeanlecode: 37

Member Stats:

Guest Posters: 1

Members: 768

Moderators: 1

Admins: 6

Forum Stats:

Groups: 13

Forums: 42

Topics: 842

Posts: 3347

Moderators: W Pirkle: 689