Closed ChzenChzen closed 2 years ago
I'm having issues replicating this when running on the same arch, same lockfile, and same cargo version. Everything works on my end. Have you tried removing your target
directory and recompiling? Can you confirm that the zip lockfile you provided is correct?
On a side note I'd recommend just committing a lockfile to a project like this. You want to make sure you have reproducible builds and not rely on having a copy of a lockfile outside of git.
Another side note is there is a published docker image to avoid having to duplicate the dockerfile, if you want.
@austinabell I found a solution, if I make default-members
in root Cargo.toml
and include only contract crates here, all compile without issues. test_utils
crate has dependency near-sdk-sim
which have the issue while compilation process to wasm.
@austinabell I found a solution, if I make
default-members
in rootCargo.toml
and include only contract crates here, all compile without issues.test_utils
crate has dependencynear-sdk-sim
which have the issue while compilation process to wasm.
Nice! Glad you were able to find a solution. near-sdk-sim
can't, and shouldn't, be compiled to wasm
cargo build
works fine, but if I trycargo build --target wasm32-unknown-unknown --release
I get error.Host: OS Ubuntu 21.10
.cargo/config:
project: link
rustup show
cargo build --target wasm32-unknown-unknown --release -vvv
Cargo.lock Cargo.lock.zip
the same behaviour if I use suggested docker image link run on the same x86 linux's machine.
I already got the same error, but the solution from the previous case doesn't help now.