Cross-Platform build scripts for audio plugins
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
falkTX 01d0708658
Set __STDC_FORMAT_MACROS for mingw
1 year ago
.github Build with LTO 1 year ago
patches Use same contents for macos intel and universal builds 1 year ago
plugins Update abgate 2 years ago
plugins-todo Add description to all packaged plugins, used in macOS installer 2 years ago
setup Set __STDC_FORMAT_MACROS for mingw 1 year ago Fix cleanup script 2 years ago
.gitignore Update gitignore 2 years ago
LICENSE Add LICENSE 2 years ago Typo (line 30) 1 year ago
VERSION Bump version 2 years ago Add tweaks for qt build, off by default 2 years ago Allow to skip LV2 build 1 year ago Build with LTO 1 year ago Fix build 1 year ago Go back to old glib on macOS 1 year ago libffi is always needed on win32 1 year ago Qt was not being compiled correctly 1 year ago Fully working audacity windows build 2 years ago Fix jack2 build 1 year ago Rework how wine is handled 2 years ago
local.env export WINDRES env var for local use 1 year ago Fix jack2 version parsing 1 year ago Fix a typo 1 year ago


Build Status

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:

  • 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
  • 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
  • Package the entire collection as an installer

Additionally, PawPaw is used to build library dependencies for Carla and JACK2.

For developers

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