chugin repo review/possible restructure

[gewang]

as per Discord discussion;

spencer: "in general think something like this will help make sure the official distribution is relatively high quality

• all chugins in ccrma/chugins compile on Mac/Windows/Linux
• clear or no external build requirements (e.g. extra libraries, dependencies, are all easily obtainable for Mac/Windows/Linux)
• related to ^ should be able to build on anyones system (setting a ccrma/chugins build pipeline up w Github Actions would help a ton w this)"

also, what is a good place to put the large volume of faust2ck chugins?

@spencersalazar @nshaheed @celestebetancur

[DBraun]

Ditto this. I hope that a goal would be for the default chuck installer to ship with all the chugins.

Also, regarding external libraries, I think we should collect any submodules in a top level folder so that they can be used among multiple plugins. For example, WarpBuf needs to build libsndfile locally because the static version from brew doesn’t have a static libsndfile.a (just libsndfile.dylib). It would be useful to have this directory higher up so that any other chugin can easily link against sndfile. Same goes for libsamplerate, Faust, JUCE, etc.

Also again, I’m working on an update to FaucK that will download the latest libfaust, and this means we won’t need large binary files committed to the repo.

[spencersalazar]

also, what is a good place to put the large volume of faust2ck chugins?

is it possible to commit these just as Faust .dsp files? And have faust2ck as a submodule? This workflow would be super slick:

• make [osx|win32|linux]
  • compiles all C++-based chugins
  • runs faust2ck on all faust chugins
  • then compiles all of these too

Maybe also the Faust .dsp files can go in a separate faust or dsp folder in the repo root.

@celestebetancur what do you think?