|falkTX 4e581f19e0||4 months ago|
|.github||5 months ago|
|.travis||4 months ago|
|patches||5 months ago|
|plugins||4 months ago|
|plugins-todo||6 months ago|
|setup||4 months ago|
|.cleanup.sh||6 months ago|
|.gitignore||7 months ago|
|.travis.yml||4 months ago|
|README.md||6 months ago|
|VERSION||4 months ago|
|bootstrap-carla.sh||5 months ago|
|bootstrap-common.sh||4 months ago|
|bootstrap-jack2.sh||4 months ago|
|bootstrap-plugins.sh||4 months ago|
|bootstrap-qt.sh||4 months ago|
|build-jack2.sh||6 months ago|
|build-plugins.sh||4 months ago|
|local.env||5 months ago|
|pack-jack2.sh||6 months ago|
|pack-plugins.sh||4 months ago|
PawPaw is a Cross-Platform build scripts setup for static libraries and audio plugins
It was created out of the need of many open-source developers to easily build their stuff for macOS and Windows,
where usually dependencies are involved which need to be built manually.
In order to make audio plugins self-contained, these dependencies/libraries need to be built statically,
which most packaging projects do not do.
Also, most open-source audio plugin projects do not have binaries for macOS or Windows,
making it very difficult for users in these platforms to enjoy them.
This project was created as a way to do automated macOS and Windows builds of such projects and libraries,
so we can finally have a good collection of LV2 plugins on these system.
The same automated setup can then be re-used/extended to support other projects and applications.
PawPaw has the following goals:
Proper documentation on how to setup PawPaw for your own project will come at a later date.
But roughly all that is needed is something like:
# change dir to PawPaw root folder cd /path/to/PawPaw # build plugin dependencies for win64 target (only needed once) ./bootstrap-plugins win64 # set up environment variables for win64 builds with PawPaw static libs source local.env win64 # change dir to your own project cd /path/to/my/project # build as usual make # or whatever other build system applies