wasmer/lib/README.md

39 lines
1.6 KiB
Markdown
Raw Normal View History

# Wasmer Libraries
Wasmer is modularized into different libraries, separated into three main sections:
2019-01-22 20:23:53 +00:00
- [Runtime](#runtime)
- [Integrations](#integrations)
- [Backends](#backends)
## Runtime
2019-01-22 20:23:53 +00:00
The core of Wasmer is the runtime, which provides the necessary
abstractions to create a good user experience when embedding.
2019-01-22 20:23:53 +00:00
The runtime is divided into two main libraries:
2019-01-22 20:23:53 +00:00
- [runtime-core](./runtime-core/): The main implementation of the runtime.
- [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](./emscripten): run Emscripten-generated WebAssembly files, such as [Lua](../examples/lua.wasm) or [nginx](../examples/nginx/nginx.wasm).
2019-01-22 20:23:53 +00:00
- Go ABI: _we will work on this soon! Want to give us a hand? ✋_
- Blazor: _research period, see [tracking issue](https://github.com/wasmerio/wasmer/issues/97)_
## Backends
2019-01-22 20:23:53 +00:00
The Wasmer [runtime](./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.
2019-01-22 20:23:53 +00:00
2019-03-08 04:39:44 +00:00
Currently, we support multiple backends for compiling WebAssembly to machine code:
- [dynasm-backend](./dynasm-backend/): Dynasm backend - super fast compilation, slower runtime speed
- [clif-backend](./clif-backend/): Cranelift backend - slower compilation, normal runtime speed
- [llvm-backend](./llvm-backend/): LLVM backend - slow compilation, native runtime speed