I avoided doing this around yabridge's launch when backtraces from
crashed plugins could be useful, but that hasn't been the case for a
long time now. Stripping the libraries can save a bit of disk space when
using a ton of plugins.
Specially for @AVLinux. We currently don't build a 32-bit version of
yabridgectl though, so you'd still need that if you want to use yabridge
on an _actual_ 32-bit system.
But do suggest enabling them in the readme and enable them on the CI.
Having them enabled by default breaks clangd/ccls, which doesn't sound
like a great idea.
https://github.com/mesonbuild/meson/issues/8146
Since this would only be needed for distribution, and we're already
doing something similar for libstdc++ on the Ubuntu 18.04 build. This
moves the static linking behind a new build option.
Somehwere between yabridge 1.1.4 and 1.2.0 we apparently started
requiring newer libstc++ features, and I kind of forgot that libstdc++
needed is bound to the version of g++ the program was compiled with.
Statically linking libstdc++ could in theory cause issues, but I think
we'll be fine.
These are now built into the image since building the minimal version of
Boost we need took minutes on the CI machines even though it should only
a few seconds.
Squash of the following commits:
WIP: Build workflow on all branches
WIP: Reduce noise from wget
WIP: Don't use bash-style redirects
WIP: Use variables for Boost url and checksum
WIP: Manually set a Wine prefix
The user that's executing the job does not own the home directory for
some reason.
WIP: Fix typos in workflow
WIP: Don't use bash-style brace expansion
This is run under dash.
WIP: Fix archive name for Ubuntu 20.04 build
WIP: Fetch tags for git-describe
WIP: Fetch all git history for git-describe
WIP :Rename the workflow
Since this is what will appear on the status badge.
Robbert van der Helm