fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 14:25:32 +00:00
Code Issues Projects Releases Wiki Activity
ad70caff83
wasmer/lib
History
Johan Andersson ad70caff83 Remove colored CLI output from runtime-core lib. 
When the colored output was originally added in https://github.com/wasmerio/wasmer/pull/489 and there was a discussion then about that it should ideally be in a higher-level crate rather than in the runtime-core library crate.

I agree with that, users of the library shouldn't be required to bring in the colored crate dependency and ideally also not have stdout/stderr output either, that should be controlled by the application that uses wasmer-runtime-core, not the library.

Disabling stdout/stderr output would be more intrusive but I wanted to at least not have colored output and another crate dependency so this change removes the colored output and the "colored" crate.
2019-09-15 03:21:04 +02:00
..
clif-backend Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
dev-utils Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
emscripten Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
emscripten-tests Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
kernel-loader Improved docs with custom logo and favicon 2019-09-03 17:06:31 -07:00
kernel-net Improved docs with custom logo and favicon 2019-09-03 17:06:31 -07:00
llvm-backend Implement atomic load and store instructions with actual atomics in the LLVM backend. 2019-09-13 12:05:55 -07:00
middleware-common Add required-by-cargo version pinning in manifest for middleware-common 2019-09-12 12:51:39 -07:00
middleware-common-tests Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime-abi Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime-c-api Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime-core Remove colored CLI output from runtime-core lib. 2019-09-15 03:21:04 +02:00
singlepass-backend Remove colored CLI output from runtime-core lib. 2019-09-15 03:21:04 +02:00
spectests Copy the spectest repository license from the official WebAssembly testsuite. These tests are under that license. 2019-09-13 13:37:48 -07:00
wasi Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
wasi-tests Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
win-exception-handler Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Renamed dynasm backend to singlepass 2019-04-11 12:44:03 -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:

  • WASI: run WebAssembly files with the WASI ABI.
  • 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 multiple backends for compiling WebAssembly to machine code:

  • singlepass-backend: Single pass backend - super fast compilation, slower runtime speed
  • clif-backend: Cranelift backend - slower compilation, normal runtime speed
  • llvm-backend: LLVM backend - slow compilation, native runtime speed