fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 22:25:40 +00:00
Code Issues Projects Releases Wiki Activity
8ed340b6f1
wasmer/lib
History
Ivan Enderlin 8ed340b6f1 fix(runtime-c-api) Update cbindgen. 
When requiring `wasmer-runtime-c-api`, I get the following conflicts:

```
error: failed to select a version for `serde_derive`.
    ... required by package `cbindgen v0.7.1`
    ... which is depended on by `wasmer-runtime-c-api v0.2.1`
    ... which is depended on by `foo v0.1.0 (/private/tmp/foo)`
versions that meet the requirements `= 1.0.58` are: 1.0.58

all possible versions conflict with previously selected packages.

  previously selected package `serde_derive v1.0.89`
    ... which is depended on by `wasmer-runtime-core v0.2.1`
    ... which is depended on by `wasmer-runtime-c-api v0.2.1`
    ... which is depended on by `foo v0.1.0 (/private/tmp/foo)`

failed to select a version for `serde_derive` which could resolve this conflict
```

This issue resolves by updating `cbindgen` to 0.8.
2019-03-05 14:28:35 +01:00
..
clif-backend Change RuntimeError type (#234) 2019-03-04 12:57:26 -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 fix(runtime-c-api) Update cbindgen. 2019-03-05 14:28:35 +01:00
runtime-core Change RuntimeError type (#234) 2019-03-04 12:57:26 -08:00
spectests Change RuntimeError type (#234) 2019-03-04 12:57:26 -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: