Closed mhhollomon closed 10 months ago
Not sure if it can help since I never used github actions, but I noticed your artifact_path
in .github/workflows/cmake.yml
points to VST3/Starp.vst3/Contents/x86_64-win/Starp.so
for the ubunut-latest
build, while I guess it should be VST3/Starp.vst3/Contents/x86_64-linux/Starp.so
.
As a side note in Linux, at least, you need the full path to have a valid bundle recognized as such by different VST3 hosts/DAWs.
If you want to publish a Linux release would be better to have a zip (or other compressed format) containing the whole Starp.vst3 folder. The content of that file should looks like this:
Starp.vst3/
└── Contents
└── x86_64-linux
└── Starp.so
Thanks @crshrprt . That is useful info about VST3s on Linux.
What DAW are you using on Linux ? Ardour ? Linux Reaper ?
BespokeSynth mainly, sometimes Ardour.
Nice! BespokeSynth looks like a great place to mine for ideas on the build system. Thanks!
Would you be willing to write a 1 or 2 paragraph install instruction for linux ?
It's just a matter of copying the resulting Starp.vst3
folder (from Starp/build/Source/Starp_artefacts/VST3/
or the release compressed file) into your ~/.vst3/
folder.
Is there a system wide directory ? Like /usr/local/share/vst3 or something ?
There are two main paths for system wide installation:
/usr/lib/vst3
when installed by the package manager
/usr/local/lib/vst3
if installed by the user
In both cases you need superuser privileges to create/copy files there.
Fixed.