pallet-revive: Use custom target to build test fixtures (#6266)
This removes the need to use a custom toolchain to build the contract test fixtures. Instead, we supply a custom target and use the currently in use upstream toolchain. --------- Co-authored-by:Jan Bujak <jan@parity.io> Co-authored-by:
Cyrill Leutwiler <cyrill@parity.io> Co-authored-by: command-bot <>
parent
cc4fe1ec
Showing
- Cargo.lock 35 additions, 21 deletionsCargo.lock
- substrate/frame/revive/Cargo.toml 0 additions, 2 deletionssubstrate/frame/revive/Cargo.toml
- substrate/frame/revive/fixtures/Cargo.toml 1 addition, 1 deletionsubstrate/frame/revive/fixtures/Cargo.toml
- substrate/frame/revive/fixtures/build.rs 31 additions, 24 deletionssubstrate/frame/revive/fixtures/build.rs
- substrate/frame/revive/fixtures/build/Cargo.toml 1 addition, 1 deletionsubstrate/frame/revive/fixtures/build/Cargo.toml
- substrate/frame/revive/fixtures/contracts/oom_rw_included.rs 6 additions, 1 deletionsubstrate/frame/revive/fixtures/contracts/oom_rw_included.rs
- substrate/frame/revive/fixtures/contracts/oom_rw_trailing.rs 6 additions, 1 deletionsubstrate/frame/revive/fixtures/contracts/oom_rw_trailing.rs
- substrate/frame/revive/fixtures/riscv32emac-unknown-none-polkavm.json 26 additions, 0 deletions...ame/revive/fixtures/riscv32emac-unknown-none-polkavm.json
- substrate/frame/revive/src/limits.rs 1 addition, 1 deletionsubstrate/frame/revive/src/limits.rs
- substrate/frame/revive/uapi/Cargo.toml 1 addition, 1 deletionsubstrate/frame/revive/uapi/Cargo.toml
Please register or sign in to comment