Linux remains the baseline release build. macOS and Windows are now configured as best-effort release package builds while their host validation is still being proven.
- Linux
linux-x86_64builds and packages onubuntu-24.04. - macOS now uses
distrho/dpf-cmake-action@v1with its explicit universalmacos-10.15target onmacos-15. The action supplies the architecture, deployment-target, and DPF-specific setup; downspout then repackages itsbin/*.vst3output into the normal zip/checksum format. - Windows now uses the same action’s
win64target fromubuntu-22.04. This uses the DPF-tested MinGW/Wine cross-build setup rather than the repository’s generic CMake toolchain path. The generated bundles are repackaged byscripts/package-built-bundles.sh. - The DPF action’s non-Linux package jobs disable
BUILD_TESTINGand Sidecar: tests are not useful during a cross-package build, and Sidecar has additional Linux-only runtime dependencies. - A local Windows package smoke succeeded on Linux after installing MinGW:
/tmp/downspout-win-package-dist/downspout-ci-local-windows-x86_64-vst3.zip. The archive contained the expectedContents/x86_64-win/*.vst3layout for the release plugin set. release.ymlmarks macOS and Windows ascontinue-on-error. Linux remains the required release asset; non-Linux packages are included when they build.
Install the Windows cross-build toolchain with:
sudo apt-get update
sudo apt-get install -y --no-install-recommends \
binutils-mingw-w64-x86-64 \
g++-mingw-w64-x86-64 \
mingw-w64 \
winewine is not required for the current package build because tests are skipped,
but it will be needed when cross-built test execution or validation is enabled.
Local references:
/home/danny/github/dpf-cmake-action/home/danny/github/PawPaw
Upstream sources:
Relevant observations from those references:
- DPF's reference Windows builds use Linux runners with MinGW/Wine, not native Windows/MSVC runners; the action also sets the compiler-ar/randlib and VST3 architecture values that the old generic path omitted.
- DPF's reference macOS builds use explicit architecture and deployment target settings and package the DPF bundle output on the macOS runner.
- PawPaw is still useful if future plugin dependencies need cross-built support beyond the current DPF-only dependency set.
- Run the updated CI workflow on GitHub and inspect the
macos-universalandwindows-x86_64artifacts. - If the Windows GitHub runner succeeds, keep the MinGW path and consider making Windows non-experimental after at least one tagged release produces a usable package.
- Validate the Windows VST3 package in a Windows DAW or plugin scanner. The build artifact exists locally, but runtime host loading has not been proven.
- Validate the macOS universal package on both Apple Silicon and Intel hosts,
or at least with
file/lipo -infoplus a plugin scan on one macOS machine. - Re-enable some Windows validation later by either setting
CMAKE_CROSSCOMPILING_EMULATOR=winefor selected core tests or adding a separate lightweight Wine smoke test. Keep package generation separate from full validation until it is stable. - If Windows CI remains slow, add a package-only CMake target or disable core
test executable targets for cross-package builds so
cmake --builddoes not compile unused.exetests. - If macOS or Windows still fails on GitHub Actions, compare the failing step with the pinned DPF action release before changing downspout’s portable plugin code.