wasmer/lib
Ivan Enderlin 7c56d893c2 feat(runtime-c-api) Generate the C header file in OUT_DIR.
This patch changes the directory where the C header files are
generated, from `CARGO_MANIFEST_DIR` to `OUT_DIR`. The goal is: When
`wasm-runtime-c-api` is used as a dependency of another Rust project,
then the C header files are accessible in the `target/` directory
(i.e. the `OUT_DIR`).

Also, since `rustc` has a `--out-dir` directory, it increases the
flexibility of this approach: The user can generate the C header files
where she wants.
2019-03-06 10:42:06 +01:00
..
clif-backend Change RuntimeError type (#234) 2019-03-04 12:57:26 -08:00
emscripten Updated version to 0.2.1 2019-02-27 17:20:49 -08:00
runtime Updated version to 0.2.1 2019-02-27 17:20:49 -08:00
runtime-c-api feat(runtime-c-api) Generate the C header file in OUT_DIR. 2019-03-06 10:42:06 +01:00
runtime-core Change RuntimeError type (#234) 2019-03-04 12:57:26 -08:00
spectests Change RuntimeError type (#234) 2019-03-04 12:57:26 -08:00
win-exception-handler fix appveyor installer and build (#224) 2019-03-01 13:16:32 -08:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Fix formatting and grammar in documentation 2019-02-19 17:01:44 -07:00

Wasmer Libraries

Wasmer is modularized into different libraries, separated into three main sections:

Runtime

The core of Wasmer is the runtime, which provides the necessary abstractions to create a good user experience when embedding.

The runtime is divided into two main libraries:

  • runtime-core: The main implementation of the runtime.
  • runtime: Easy-to-use API on top of runtime-core.

Integrations

The integration builds on the Wasmer runtime and allow us to run WebAssembly files compiled for different environments.

Wasmer intends to support different integrations:

  • emscripten: run Emscripten-generated WebAssembly files, such as Lua or nginx.
  • Go ABI: we will work on this soon! Want to give us a hand?
  • Blazor: research period, see tracking issue

Backends

The Wasmer runtime is designed to support multiple compiler backends, allowing the user to tune the codegen properties (compile speed, performance, etc) to best fit their use case.

Currently, we support a Cranelift compiler backend: