Skip to content
Snippets Groups Projects

update srtool build instructions

Merged Hugo Trentesaux requested to merge hugo-runtime-801-instructions into master
1 unresolved thread

These changes come from the runtime-801 branch and were not merged into master, leading to people not knowing that they were using a more recent version of the runtime. This is linked to #195 (closed). I'm merging this until we improve the branching strategy.

Merge request reports

Pipeline #36991 waiting for manual action

Pipeline waiting for manual action for 9af50b42 on hugo-runtime-801-instructions

Merged by Hugo TrentesauxHugo Trentesaux 1 year ago (May 14, 2024 2:03pm UTC)

Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Hugo Trentesaux resolved all threads

    resolved all threads

  • Hugo Trentesaux added 1 commit

    added 1 commit

    Compare with previous version

  • Hugo Trentesaux marked this merge request as ready

    marked this merge request as ready

  • Hugo Trentesaux changed title from Draft: update runtime version and build instructions to update srtool build instructions

    changed title from Draft: update runtime version and build instructions to update srtool build instructions

  • Hugo Trentesaux added 5 commits

    added 5 commits

    Compare with previous version

  • removed RN-runtime label

  • changed milestone to %runtime-802

  • Hugo Trentesaux mentioned in commit 6bc8c9c9

    mentioned in commit 6bc8c9c9

  • 2 2
    3 3 When voting for a runtime upgrade, you should check that the proposed hash actually corresponds to the published code you reviewed. Otherwise, a malicious runtime upgrade could be advertised as a legitimate one.
    4 4
    5 ```docker
    5 ```sh
    6 mkdir runtime/gdev/target
    7 chmod o+w runtime/gdev/target
    8 # Workaround see !239
    9 echo -e "[toolchain]\nchannel = \"1.74.0\"\ncomponents = [ \"rust-std\", \"rust-src\" ]" > runtime/gdev/rust-toolchain.toml
    6 10 docker run \
    • Cette commande fonctionne-t-elle toujours en local ? En tout cas sur la CI j'ai un échec :

      Cannot compile the WASM runtime: the `wasm32-unknown-unknown` target is not installed!

      Plus précisément les commandes à jouer sont :

      echo -e "[toolchain]\nchannel = \"`curl -s https://raw.githubusercontent.com/paritytech/srtool/master/RUSTC_VERSION`\"\ncomponents = [ \"rust-std\", \"rust-src\" ]\ntargets = [ \"wasm32-unknown-unknown\" ]" > gdev/rust-toolchain.toml
      docker run \
        -i \
        --rm \
        -e PACKAGE=gdev-runtime \
        -e RUNTIME_DIR=runtime/gdev \
        -v $PWD:/build \
        paritytech/srtool:1.77.0-0.15.0 build --app --json -cM

      cc @bgallois

    • Evidemment il suffit que j'écrive le message pour trouver le contournement : il suffit de retirer la partie targets =, voici l'instruction qui fonctionne en local :

      echo -e "[toolchain]\nchannel = \"`curl -s https://raw.githubusercontent.com/paritytech/srtool/master/RUSTC_VERSION`\"\ncomponents = [ \"rust-std\", \"rust-src\" ]" > gdev/rust-toolchain.toml
    • Please register or sign in to reply
    Please register or sign in to reply
    Loading