Closed JoshOrndorff closed 1 year ago
Looking into this, but let me say that the CI always ensures that the project builds on latest ubuntu.
See: https://github.com/paritytech/ink-playground/blob/main/.github/workflows/rust.yml
and: https://github.com/paritytech/ink-playground/actions/runs/5123640814/jobs/9214439679
Just checked, we indeed execute not the full set of Docker commands directly in the CI, but we handle this in the Dockerfile:
https://github.com/paritytech/ink-playground/blob/main/Dockerfile
which ich build as part of the CI:
https://github.com/paritytech/ink-playground/blob/main/.github/workflows/docker.yml
See the last successfull CI run here:
https://github.com/paritytech/ink-playground/actions/runs/5123640812/jobs/9214439915
@JoshOrndorff can you please try the following command:
make clean
rustup toolchain install nightly-2022-05-24
rustup component add rust-src --toolchain nightly-2022-05-24-x86_64-unknown-linux-gnu
curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh
And afterwards again:
make install
make generate
make backend-run
make generate
succeeds when I run these you suggested commands. Indeed I had already worked around this by installing the right toolchain as I reported at the end of the original issue. I just reported this so that you could improve the script so others don't hit this bump.
However, make backend-run
still fails as I reported in #728
Was a machine setup problem which is now solved by adding conditional wasm-pack
installation to the Makefile by https://github.com/paritytech/ink-playground/pull/735.
The
make generate
command in the readme fails to complete with the following output. I use this Ubuntu 22.04 system for daily Substrate work, but this is my first endeavor into ink!.Running the suggested
rustup component add rust-src --toolchain nightly-2022-05-24-x86_64-unknown-linux-gnu
and trying again gets past this problem, but still I guess the make script should get this right.