Hi there,
Your project looks interesting, building cross-platform plugins in an automated way.
I've also been trying to solve this problem and come up with a slightly different approach. It could be useful for your project. Instead of trying to create an uber single project which can build any type of plugin, separating them into framework-specific projects.
My approach:
Template repo named after a framework (Dplug, iPlug, JUCE, Steinberg)
Framework as a git submodule (so it's linked but not stored in the same repo and don't infringe copyright)
./src/ folder to contain any custom code/assets
README.md containing the commands to build the plugin locally
./github/workflows folder containing the release workflow to build the commands cross-platform
So far i've created boilerplate repos for the main framework types here:
If we can help plugin developers to start structuring their plugins with automated builds, they will save time, there will be more compatibility and everyone will benefit!
Hi there, Your project looks interesting, building cross-platform plugins in an automated way.
I've also been trying to solve this problem and come up with a slightly different approach. It could be useful for your project. Instead of trying to create an uber single project which can build any type of plugin, separating them into framework-specific projects.
My approach:
So far i've created boilerplate repos for the main framework types here:
Feel free to copy/reused the same approach :)
If we can help plugin developers to start structuring their plugins with automated builds, they will save time, there will be more compatibility and everyone will benefit!