fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 06:15:33 +00:00
Code Issues Projects Releases Wiki Activity
d31c1c6068
wasmer/lib
History
Brandon Fish d31c1c6068 Fix lints
2019-02-02 18:07:37 -06:00
..
clif-backend Add Pages and Bytes newtypes 2019-01-29 15:44:15 -08:00
emscripten Comment out em impl to fix compilation 2019-01-29 20:00:08 -06:00
runtime Add Pages and Bytes newtypes 2019-01-29 15:44:15 -08:00
runtime-c-api Fix lints 2019-02-02 18:07:37 -06:00
runtime-core Merge branch 'master' into feature/move-spectests-to-own-lib 2019-01-29 19:04:10 -06:00
spectests Merge branch 'master' into feature/move-spectests-to-own-lib 2019-01-29 19:04:10 -06:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Improved docs 2019-01-22 12:23:53 -08:00

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 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: 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: researching 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 fit your usecase best.

Currently, we support a Cranelift compiler backend: