Strip shared libraries?

[webmaster128]

Stripping is currently disabled. We could (should?) re-enable it. It must be performed in the guest (the builder) in order to support stripping for multiple systems.

[ethanfrey]

It was disabled to allow easier debugging if we hit a crash in Rust, which had happened before due to some race conditions.

Once we hit 1.0, we could strip again, and only make custom builds if we need to debug something.

[webmaster128]

Is there any value in having a small binary for the shared library? One could argue the symbols do not hurt and may help debug exotic crashed on live chains.

If we want to enable stripping, I suggest letting Rust do it directly. There are two ways:

1. Current workaround: RUSTFLAGS='-C link-arg=-s' cargo build --release
2. The almost stable cargo configuration: Tracking issue for -Z strip=val option rust-lang/rust#72110

For now, I'll remove all reference to extra OS specific strip tools.

[ethanfrey]

5MB off of a 50-60MB wasmd binary is not a major issue IMO.

We could see what the size difference is with the stripped/unstripped DLLs. And then the current size of wasmd and guess what this will effect. But I don't see too much need to optimize for binary size.