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
1dfa106850
wasmer/lib
History
Brandon Fish 1dfa106850 Add C API module import descriptors
2019-02-23 18:25:51 -06:00
..
clif-backend Fix after merge 2019-02-22 14:07:03 -08:00
emscripten more emscripten stubs and urandom hack (#199) 2019-02-22 10:42:38 -08:00
runtime Fix after merge 2019-02-22 14:07:03 -08:00
runtime-c-api Add C API module import descriptors 2019-02-23 18:25:51 -06:00
runtime-core Create a grow error and refactor grow impl to return result (#191) 2019-02-22 22:18:59 -08:00
spectests Merge branch 'master' into feature/cache-rework 2019-02-21 11:54:57 -08:00
win-exception-handler remove unnecessary print statements (#177) 2019-02-14 11:11:35 -08:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Fix formatting and grammar in documentation 2019-02-19 17:01:44 -07: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 integration builds on 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: research 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 best fit their use case.

Currently, we support a Cranelift compiler backend: