$ ~/binaryen-version_108/bin/wasm-opt --version
wasm-opt version 108 (version_108)
Probably this is because we are using the same logic to pull out the git tag and I hadn't tagged the release. I am also using a different tagging scheme.
I am not sure the solution to this off hand, whether we should reproduce exactly the string that Binaryen uses or not.
When installed from cargo I see this:
Binaryen looks like
Probably this is because we are using the same logic to pull out the git tag and I hadn't tagged the release. I am also using a different tagging scheme.
I am not sure the solution to this off hand, whether we should reproduce exactly the string that Binaryen uses or not.