mirror of
https://github.com/fluencelabs/wasmer
synced 2024-12-13 22:25:40 +00:00
37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
# Wasmer Libraries
|
|
|
|
Wasmer is modularized into different libraries, separated into three main sections:
|
|
|
|
- [Runtime](#Runtime)
|
|
- [Integrations](#Integrations)
|
|
- [Backends](#Backends)
|
|
|
|
## 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](./runtime-core/): The main implementation of the runtime.
|
|
- [runtime](./runtime/): Easy-to-use api on top of runtime-core.
|
|
|
|
## Integrations
|
|
|
|
The intergration run on-top of the Wasmer runtime and allow us to run WebAssembly files compiled for different environments.
|
|
|
|
Wasmer intends to support different integrations:
|
|
|
|
- [emscripten](./emscripten): run emscripten-generated WebAssembly files, such as [Lua](../examples/lua.wasm) or [Nginx](../examples/nginx/nginx.wasm).
|
|
- Go ABI: _we will work on this soon! Want to give us a hand? ✋_
|
|
- Blazor: _researching period, see [tracking issue](https://github.com/wasmerio/wasmer/issues/97)_
|
|
|
|
## Backends
|
|
|
|
The Wasmer [runtime](./runtime) is designed to support multiple compiler backends, allowing the user
|
|
to tune the codegen properties (compile speed, performance, etc) to fit your usecase best.
|
|
|
|
Currently, we support a Cranelift compiler backend:
|
|
|
|
- [clif-backend](./clif-backend/): The integration of Wasmer with Cranelift
|