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
6c7fd55b87
wasmer/lib
History
Syrus 6c7fd55b87 Moved ctx to be the first argument in emscripten
2019-02-09 13:58:18 -08:00
..
clif-backend fix windows linking and appveyor build (#166) 2019-02-08 13:51:29 -08:00
emscripten Moved ctx to be the first argument in emscripten 2019-02-09 13:58:18 -08:00
runtime Add caching. (#134) 2019-02-06 16:26:45 -08:00
runtime-core Moved ctx in func macro to be first arg 2019-02-09 13:33:22 -08:00
spectests Naive short circuiting implementation for user panics and results. (#167) 2019-02-08 13:08:03 -08: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: