I’m a bit of a ta-ta trying to build on Ubuntu (18.04) - I’ve read a few of the posts from the past about this, looked around Git etc and managed to resolve one or two issues but I’m still unable to build.
Things I’ managed to get to work:
I have CSound installed. I’ve have Producer built.
My cabbasge directory is under home:
My Juce folder is at
My SDK folder is at
Into which I’ve got the current VST3 SDK unzipped:
I’m also in posession of the old VST2.4 SDK which I’ve used in the past but I’m really only wanting to compile to VST3 at the moment.
CSound did not install to the folders that the Juce build required but I’ve found the relevant locations and have been using
./buildCabbage “usr/include/csound” “usr/lib/csound” “/home/me/SDKs/VST_SDK”
The two issues I’ve got are that the build fails with
…/…/JuceLibraryCode/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:87:10: fatal error: pluginterfaces/vst2.x/aeffect.h: No such file or directory
aeffect.h is definitely within my SDK folder under
where it should be
I’ve also tried to build with just the 2.4 SDK in the folder and it still fails.
I’ve also tried with the file path to legacy VSTDSK within the settings in Procujer, makes no difference. I’ve tried the VST SDK under home where it is now and also under root, no difference, and several other things, no joy, always fails.
My second failure issue is with
…/…/JuceLibraryCode/modules/juce_graphics/juce_graphics.cpp:92:12: fatal error: ft2build.h: No such file or directory
Now, I already have libwebkit2gtk 3 installed. I
I’m trying to add the ppa but get a 404 error for bionic backports.
Err:7 http://ppa.launchpad.net/webkit-team/ppa/ubuntu bionic Release
404 Not Found [IP: 18.104.22.168 80]
Which I assume means I’m going to have to flatten my system and rebuild with the latest Ubuntu (which will take a VERY long time with al the WINE stuff on here etc.) if I want to proceed with Cabbage?
I know you may not necc. know about the Webkit or a way around it but my worry is that if I spend two weeks rebuilding I’ll still have the same issue with the SDK??