mirror of
https://github.com/robbert-vdh/yabridge.git
synced 2026-05-06 19:40:10 +02:00
Strip the binaries in the CI
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.
This commit is contained in:
@@ -48,6 +48,8 @@ jobs:
|
||||
# with a newer version of g++ than what's in the default repos
|
||||
meson setup build --buildtype=release --cross-file=cross-wine.conf --unity=on --unity-size=10000 -Dwith-static-boost=true -Dwith-bitbridge=true -Dcpp_link_args='-mwindows -static-libstdc++' -Dbuild.cpp_link_args='-static-libstdc++'
|
||||
ninja -C build
|
||||
- name: Strip remaining debug symbols
|
||||
run: strip build/libyabridge-{vst2,vst3}.so build/yabridge-{host,group}{,-32}.exe.so
|
||||
- name: Create an archive for the binaries
|
||||
run: |
|
||||
mkdir yabridge
|
||||
@@ -84,6 +86,8 @@ jobs:
|
||||
# compatible with GCC 10, even if that's not the default GCC version
|
||||
meson setup build --buildtype=release --cross-file=cross-wine.conf --unity=on --unity-size=10000 -Dwith-static-boost=true -Dwith-bitbridge=true
|
||||
ninja -C build
|
||||
- name: Strip remaining debug symbols
|
||||
run: strip build/libyabridge-{vst2,vst3}.so build/yabridge-{host,group}{,-32}.exe.so
|
||||
- name: Create an archive for the binaries
|
||||
run: |
|
||||
mkdir yabridge
|
||||
@@ -122,6 +126,8 @@ jobs:
|
||||
# 32-bit OS
|
||||
meson setup build --buildtype=release --cross-file=cross-wine.conf --unity=on --unity-size=10000 -Dwith-static-boost=true -Dwith-bitbridge=true -Dcpp_link_args='-mwindows -static-libstdc++' -Dbuild.cpp_args='-m32' -Dbuild.cpp_link_args='-m32 -static-libstdc++'
|
||||
ninja -C build
|
||||
- name: Strip remaining debug symbols
|
||||
run: strip build/libyabridge-{vst2,vst3}.so build/yabridge-{host,group}{,-32}.exe.so
|
||||
- name: Create an archive for the binaries
|
||||
run: |
|
||||
mkdir yabridge
|
||||
|
||||
Reference in New Issue
Block a user