fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2025-03-16 08:10:49 +00:00
Code Issues Projects Releases Wiki Activity
wasmer/lib
History
Mackenzie Clark bde2022b58
fix appveyor installer and build (#224) 
* remove exception handler when function returns or throws

* revert to only reserving and not committing memory due to issues

* appveyor builds for release, caches more, only publish artifact once
2019-03-01 13:16:32 -08:00
..
clif-backend
Updated crates version to 0.2.0
2019-02-25 13:33:33 -08:00
emscripten
Updated version to 0.2.1
2019-02-27 17:20:49 -08:00
runtime
Updated version to 0.2.1
2019-02-27 17:20:49 -08:00
runtime-c-api
Merge branch 'master' into feature/add-c-api-module-import-descriptors
2019-03-01 12:50:35 -06:00
runtime-core
fix appveyor installer and build (#224)
2019-03-01 13:16:32 -08:00
spectests
Updated crates version to 0.2.0
2019-02-25 13:33:33 -08:00
win-exception-handler
fix appveyor installer and build (#224)
2019-03-01 13:16:32 -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: