Linux VST build deletes all files in ~/.vst
-
I don't have a back up of the folder but I can rebuild it. Most of it hopefully. This is a mess because it is going to take me a long time to rebuild.
why does the standalone get built in -> projects/standalone/Builds/LinuxMakefile/build/
and the VST gets placed in ~./vst?
thankfully it wasn't a make sudo install going to /usr/lib/vst
this is bad. very bad.the VST plugin build has to go in... projects/plugin/Builds/LinuxMakefile/build/
seriously. please correct this. depositing it in ~./vst without consent is already a bad idea
that it deletes the folder is unacceptable -
it's not that complicated
I will do it manually but I would recommend to change line 32 in
projects/plugin/Builds/LinuxMakefile/Makefilefrom
JUCE_OUTDIR := ~/.vstto
JUCE_OUTDIR := build -
I suspect what deleted the files was not the build but the
make clean -
Ah sorry about that. I assumed that the build script from the Projucer just copies the final binary as post build step - this is what it does on Windows and macOS - that it uses it as actual build folder and subsequently deletes everything in there on a clean is indeed nasty and a little bit intrusive too
-
@oddyotrax What distro do you use?
-
I don't think it was when I rebuilt the VST
before I did the rebuild, I did a make clean and I suspect that is what wiped the folder of its contents
-
d-healey Debian Stretch
-
@oddyotrax I'm using Linux Mint and I use timeshift to backup my home directory, I think it's probably available for Debian too.
-
Alright, I've updated the Projucer files so that it will not use the VST folder as build folder anymore.
Please try if it works now (best backup your VST folder again :) Be aware that you have to resave the Projucer file so that it updates your local makefile.
-
@d-healey Thanks for the suggestion. Debian has back in time... I just made zip files of the most important folders. It's all good I had copies of everything and restored everything back to working order. My apologies for freaking out.
