fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2025-03-16 16:20:49 +00:00
Code Issues Projects Releases Wiki Activity
wasmer/lib
History
Mackenzie Clark ce03e4464c fill unsetenv for windows (#150) 
* fill unsetenv

* update usage of read_string_from_wasm

* convert helper to return String

* correct usage of helper fn, cargo fmt, and check in lock file change
2019-02-07 10:51:19 -08:00
..
clif-backend
Add caching. (#134)
2019-02-06 16:26:45 -08:00
emscripten
fill unsetenv for windows (#150)
2019-02-07 10:51:19 -08:00
runtime
Add caching. (#134)
2019-02-06 16:26:45 -08:00
runtime-core
install errno on all platforms (#152)
2019-02-07 10:02:41 -08:00
spectests
Add caching. (#134)
2019-02-06 16:26:45 -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: