mirror of
https://github.com/fluencelabs/wasmer
synced 2024-12-13 14:25:32 +00:00
362e5aa160
- Come on inkwell, I thought you were better than this. |
||
---|---|---|
.. | ||
clif-backend | ||
emscripten | ||
llvm-backend | ||
runtime | ||
runtime-c-api | ||
runtime-core | ||
spectests | ||
win-exception-handler | ||
.gitignore | ||
README.md |
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:
- clif-backend: The integration of Wasmer with Cranelift