Brian Anderson

I've thought about this some more, and think there may be a way to cache `cc` build results even with `cxx_build`, at least with the limited features that wasm-opt uses....

One thing to note is that even if we skip building some C++ files, I don't see any way to avoid rerunning `ar` to create the library rustc needs to...

There is another potential approach here: sscache already does build caching for rust and C++. It could be possible to automatically acquire sccache and configure it as part of the...

I am undecided yet about whether to actually do this, as the pattern we have now is fine for our purposes, and the suggested pattern requires using C++ free functions...

I believe the C++ build of wasm-opt already respects `-C opt-level=s`, at least when the optimization level is set by cargo (I am not clear on what happens if it...

@nazar-pc I am reluctant to try to delete intermediate build artifacts as part of the build process itself, mostly because it strikes me as an atypical thing for a build...

I am interested to hear more from the substrate authors about this, as it does seem to be primarily an issue with how the substrate build is orchestrated. The issue...

Here's another issue as linked in the substrate PR: https://github.com/paritytech/substrate/issues/12671

Probably the thing to do is spend a small amount of time seeing how many changes are necessary to convert our bindings to be const-correct, and if that seems reasonable,...

I am guessing this behavior exists upstream so it might help to test the build from https://github.com/WebAssembly/binaryen and file an issue with them. The issue could be related to a...