|
|
@@ -10,14 +10,14 @@ 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, |
|
|
In order to make audio plugins self-contained, these dependencies/libraries need to be built statically, |
|
|
which most packaging projects do not do. |
|
|
which most packaging projects do not do. |
|
|
|
|
|
|
|
|
Also, most open-source audio plugin projects to do not have binaries for macOS or Windows, |
|
|
|
|
|
|
|
|
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. |
|
|
making it very difficult for users in these platforms to enjoy them. |
|
|
|
|
|
|
|
|
PawPaw has the following goals: |
|
|
PawPaw has the following goals: |
|
|
|
|
|
|
|
|
- Single script to build most common plugin dependencies statically, both natively and cross-compiling |
|
|
- Single script to build most common plugin dependencies statically, both natively and cross-compiling |
|
|
- Clean and simple code, easy to maintain and add new libraries to build |
|
|
- Clean and simple code, easy to maintain and add new libraries to build |
|
|
- Statically built LV2 plugins for (at least) macOS and Windows |
|
|
|
|
|
|
|
|
- Statically build LV2 plugins for (at least) macOS and Windows |
|
|
- Define each plugin project in its own file, to make it easy to support new plugins via pull-request |
|
|
- Define each plugin project in its own file, to make it easy to support new plugins via pull-request |
|
|
- Package the entire collection as an installer |
|
|
- Package the entire collection as an installer |
|
|
|
|
|
|
|
|
|
