Crates.io | faasm-sys |
lib.rs | faasm-sys |
version | 0.0.12 |
source | src |
created_at | 2020-03-24 23:26:15.877117 |
updated_at | 2020-03-30 11:30:40.212941 |
description | Rust bindings for Faasm. |
homepage | |
repository | https://github.com/mfournial/faasm-sys |
max_upload_size | |
id | 222491 |
size | 63,471 |
Rust bindings for Faasm.
Running the following will:
vendor
bindings.rs
file in vendor
in the librarycargo build --target wasm32-unknown-unknown
If you set the FAASM_SYS_DEV
environment variable before building, then the build script will fetch libraries according to the Faasm local development defaults. You can then run the test script as well:
env FAASM_SYS_DEV=1 cargo build --target wasm32-unknown-unknown
./bin/test.sh
Note that when used as a submodule of rust-faasm,
the target
directory is directed one level up.
Since by default cargo tries to package the downloaded files in the build script and there is no
reason we should do this, you should publish in local dev mode FAASM_SYS_DEV
only.
set -x FAASM_SYS_DEV 1
cargo publish --target wasm32-unknown-unknown