Echo https://github.com/wasmerio/wasmer-go/pull/232, current dynamically linked libwasmer makes it hard to copy go executables around. This PR adds and E2E test that builds a sample program with local wasmer-go and then check whether libwasmer is statically linked.
There'll be some other PRs to make the actual linking changes, which can be verified by this one.
P.S. I run CI job in my fork with all three changes and get result here. E2E test result shows libwasmer are statically linked successfully on both targets.
I don't have test envs to verify linux-aarch64 and darwin-aarch64 so I didn't not send PR for them, but I guess the same change should be sufficient.
Echo https://github.com/wasmerio/wasmer-go/pull/232, current dynamically linked libwasmer makes it hard to copy go executables around. This PR adds and E2E test that builds a sample program with local wasmer-go and then check whether libwasmer is statically linked.
There'll be some other PRs to make the actual linking changes, which can be verified by this one.
P.S. I run CI job in my fork with all three changes and get result here. E2E test result shows libwasmer are statically linked successfully on both targets. I don't have test envs to verify linux-aarch64 and darwin-aarch64 so I didn't not send PR for them, but I guess the same change should be sufficient.