Files
pezkuwi-subxt/substrate/client/executor
Bastian Köcher 923cb8eea1 Wasm-builder 3.0 (#7532)
* Build every wasm crate in its own project with wasm-builder

Building all wasm crates in one workspace was a nice idea, however it
just introduced problems:

1. We needed to prune old members, but this didn't worked for old git
deps.
2. We locked the whole wasm workspace while building one crate. This
could lead to infinitely locking the workspace on a crash.

Now we just build every crate in its own project, this means we will
build the dependencies multiple times. While building the dependencies
multiple times, we still decrease the build time by around 30 seconds
for Polkadot and Substrate because of the new parallelism ;)

* Remove the requirement on wasm-builder-runner

This removes the requirement on wasm-builder-runner by using the new
`build_dep` feature of cargo. We use nightly anyway and that enables us
to use this feature. This solves the problem of not mixing
build/proc-macro deps with normal deps. By doing this we get rid off
this complicated project structure and can depend directly on
`wasm-builder`. This also removes all the code from wasm-builder-runner
and mentions that it is deprecated.

* Copy the `Cargo.lock` to the correct folder

* Remove wasm-builder-runner

* Update docs

* Fix deterministic check

Modified-by: Bastian Köcher <git@kchr.de>

* Try to make the ui test happy

* Switch to `SKIP_WASM_BUILD`

* Rename `SKIP_WASM_BINARY` to the correct name...

* Update utils/wasm-builder/src/builder.rs

Co-authored-by: André Silva <123550+andresilva@users.noreply.github.com>

* Update utils/wasm-builder/src/builder.rs

Co-authored-by: André Silva <123550+andresilva@users.noreply.github.com>

Co-authored-by: André Silva <123550+andresilva@users.noreply.github.com>
2020-11-24 10:18:36 +01:00
..
2020-10-20 12:41:51 +00:00
2020-11-24 10:18:36 +01:00
2020-10-20 12:41:51 +00:00
2020-11-13 13:48:23 +00:00
2020-10-20 12:41:51 +00:00
2020-08-20 17:04:42 +02:00

A crate that provides means of executing/dispatching calls into the runtime.

There are a few responsibilities of this crate at the moment:

  • It provides an implementation of a common entrypoint for calling into the runtime, both wasm and compiled.
  • It defines the environment for the wasm execution, namely the host functions that are to be provided into the wasm runtime module.
  • It also provides the required infrastructure for executing the current wasm runtime (specified by the current value of :code in the provided externalities), i.e. interfacing with wasm engine used, instance cache.

License: GPL-3.0-or-later WITH Classpath-exception-2.0