Alternatively just install Ninja, use “-G Ninja” which is more efficient and debug with CLion (and this is coming from a former VS fanboy …). Shout-out to benvining for encouraging me to move to CLion with his posts on the forum.
Yes. You have set the folder of the build files with -B Builds/Debug. With CLion you can save the cmake arguments, choose options with friendly dropdown menus, specify the output build folder and then click a button, so that keeps you out of the command line (as I said, this is coming from a previous VS heavy user ;P)
Run cmake where Cmakelists.txt is placed. Everything that cmake needs is in Cmakelists.txt (well and the package manager files if you are using one for dependencies, like vcpkg).
CMake Error at CMakeLists.txt:25 (add_subdirectory):
The source directory
C:/Users/sk/Desktop/pluginval-1.0.4/modules/juce
does not contain a CMakeLists.txt file.
Indeed, that folder is empty. I assume I have to download juce source into it first?
Run something like the following in the `pluginval-1.0.4` directory to grab JUCE module, though I would guess downloading JUCE directly would also work:
Thank you. I downloaded and installed git, which I have not used before.
I tried this from within the `pluginval-1.0.4` directory, but its’ not working:
C:\Users\sk\Desktop>chdir pluginval-1.0.4
C:\Users\sk\Desktop\pluginval-1.0.4>git submodule update --init --recursive
fatal: not a git repository (or any of the parent directories): .git
C:\Users\sk\Desktop\pluginval-1.0.4>git submodule update --init
fatal: not a git repository (or any of the parent directories): .git
Oh, I got it. You download the code directly. Could you please run the following directly on your desktop to clone the pluginval code:
git clone https://github.com/Tracktion/pluginval
Then, under the pluginval directory, you should be able to run:
git checkout v1.0.4 // it seems that the current tip of the develop load JUCE from CPM and the current README is outdated, so you may want the v1.0.4
// actually using CPM might be good so you can skip the following
// but I haven't updated pluginval for a while so cannot say much about that
git submodule update --init --recursive
Of course, the previous method might still work, i.e., directly put JUCE code under the modules/.
EDIT:
no, that seems wrong. There is something in there:
if (DEFINED ENV{VST2_SDK_DIR})
MESSAGE(STATUS "Building with VST2 SDK: $ENV{VST2_SDK_DIR}")
juce_set_vst2_sdk_path($ENV{VST2_SDK_DIR})
else()
MESSAGE(STATUS "Not building with VST2")
endif()
-- Finished setting up juceaide
-- Building with VST2 SDK: C:\Development\SDKs\VST2_SDK
-- Configuring done (1.6s)
-- Generating done (0.5s)
-- Build files have been written to: C:/Users/sk/Desktop/pluginval/Builds/Debug