How to install the VST3SDK package?

[O.F.I.N.S.I.S.]

Hi.

I compiled VST3SDK successfully. Compiled the sources package available from steinberg.com. Used this as the git sources failed by a missing file.

Though, the compiled package doesn't seem to have the ability to be installed via make install or new2dir make install.

It complains about the install command after compiling finished by make.

So, where to install files after compiling and/or what needs to be installed?

Else: anyone got a ready for use installation package (64bit) of VST3SDK available?

[rockedge]

I will have to look into it. Can you post the cmake or gcc log file?
There are package builds that only have a "make" and no "make install". In that case there should be binaries or libraries created. Compiling Darknet-YOLO for example works this way with only "make". With Darknet one can run it from the build directory or I move it to somewhere in the $PATH. Like /root/my-applications/bin

can you do a global file search and see if any binaries were created?
Or look into the source code directory...are there any binaries now in that directory?

[O.F.I.N.S.I.S.]

Inside of the build directory, there's a lot of binaries created. The build directory is: 594 M (843 Files, 302 Directories).

Path (...) is: /root/Dateien/Downloads/apps/Compile-VST3SDK-Additions

The bin directory contains:

.../VST_SDK/VST3_SDK/build/bin/Debug/ImageStitcher/ImageStitcher

.../VST_SDK/VST3_SDK/build/bin/Debug/audiohost
.../VST_SDK/VST3_SDK/build/bin/Debug/editorhost
.../VST_SDK/VST3_SDK/build/bin/Debug/uidesccompressor
.../VST_SDK/VST3_SDK/build/bin/Debug/validator

.../VST_SDK/VST3_SDK/build/CMakeFiles/feature_tests.bin

.../VST_SDK/VST3_SDK/build/CMakeFiles/3.10.2/CompilerIdC/a.out
.../VST_SDK/VST3_SDK/build/CMakeFiles/3.10.2/CompilerIdCXX/a.out

.../VST_SDK/VST3_SDK/build/CMakeFiles/3.10.2/CMakeDetermineCompilerABI_C.bin
.../VST_SDK/VST3_SDK/build/CMakeFiles/3.10.2/CMakeDetermineCompilerABI_CXX.bin

The lib directory contains (no binaries, but files):

.../VST_SDK/VST3_SDK/build/lib/Debug/libbase.a
.../VST_SDK/VST3_SDK/build/lib/Debug/libpluginterfaces.a
.../VST_SDK/VST3_SDK/build/lib/Debug/libsdk.a
.../VST_SDK/VST3_SDK/build/lib/Debug/libvstgui.a
.../VST_SDK/VST3_SDK/build/lib/Debug/libvstgui_standalone.a
.../VST_SDK/VST3_SDK/build/lib/Debug/libvstgui_support.a
.../VST_SDK/VST3_SDK/build/lib/Debug/libvstgui_uidescription.a

The VST3 directory contains directories:

.../VST_SDK/VST3_SDK/build/VST3/Debug/adelay.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/againsimple.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/again.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/channelcontext.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/helloworld.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/helloworldWithVSTGUI.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/hostchecker.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/legacymidiccout.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/mda-vst3.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/noteexpressionsynth.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/noteexpressiontext.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/pitchnames.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/prefetchablesupport.vst3
.../VST_SDK/VST3_SDK/build/VST3/Debug/programchange.vst3

Each one of these directories contains its related .so library file in sub-directories:

.../VST_SDK/VST3_SDK/build/VST3/Debug/adelay.vst3/Contents/x86_64-linux/adelay.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/againsimple.vst3/Contents/x86_64-linux/againsimple.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/again.vst3/Contents/x86_64-linux/again.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/channelcontext.vst3/Contents/x86_64-linux/channelcontext.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/helloworld.vst3/Contents/x86_64-linux/helloworld.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/helloworldWithVSTGUI.vst3/Contents/x86_64-linux/helloworldWithVSTGUI.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/hostchecker.vst3/Contents/x86_64-linux/hostchecker.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/legacymidiccout.vst3/Contents/x86_64-linux/legacymidiccout.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/mda-vst3.vst3/Contents/x86_64-linux/mda-vst3.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/noteexpressionsynth.vst3/Contents/x86_64-linux/noteexpressionsynth.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/noteexpressiontext.vst3/Contents/x86_64-linux/noteexpressiontext.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/pitchnames.vst3/Contents/x86_64-linux/pitchnames.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/prefetchablesupport.vst3/Contents/x86_64-linux/prefetchablesupport.so
.../VST_SDK/VST3_SDK/build/VST3/Debug/programchange.vst3/Contents/x86_64-linux/programchange.so

Some of these directories containing also a sub-directory, e.g.: /pitchnames.vst3/Contents/Resources

[O.F.I.N.S.I.S.]

Ok, thanks for the support.

After examining the configure script, I found a special compiler option to define a path to the compiled VST3SDK.
So, it doesn't need to be installed at all.
I was able to compile Qtractor 0.9.15 with VST3 enabled by using a compiler option: --with-vst3=PathToVST3SDK.

Now I'm going to upload the .pet plus .deb packages to my google drive.