You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Pat Hickey 71d279a4b0 wasi-headers: unions are tagged now 5 years ago
.github/workflows fix macos filename, use https 5 years ago
basics Move math source files. (#151) 5 years ago
dlmalloc Convert more wasi-libc code to `//`-style comments. (#153) 5 years ago
expected/wasm32-wasi Avoid using cast expressions in WASI API constants. (#148) 5 years ago
libc-bottom-half Remove unused cloudlibc headers. (#170) 5 years ago
libc-top-half Define a_clz_32 for musl so that it doesn't use a software version. (#171) 5 years ago
tools/wasi-headers wasi-headers: unions are tagged now 5 years ago
.gitattributes Correct the version of #136 on master (#141) 5 years ago
.gitignore gitignore build 6 years ago
.gitmodules Correct the version of #136 on master (#141) 5 years ago
CODE_OF_CONDUCT.md Add a CODE_OF_CONDUCT.md file. (#101) 5 years ago
LICENSE WASI libc prototype implementation. 6 years ago
Makefile Move math source files. (#151) 5 years ago
README.md Update docs to say "libc" rather than "sysroot" where applicable. 5 years ago

README.md

WASI Libc

This is a work in progress. It's usable for many purposes, though the APIs aren't stable yet.

What is this?

It's several things.

First, it's a usable libc. It builds a "libc" which can be used by compilers, such as Clang 8.0, using the wasm32-wasi target. It's a work in progress, but it is already sufficient to run basic programs.

Second, it's a "reference" implementation, which means the interfaces defined here can be used by other tools and libraries, even if they don't use all the actual implementations here. For example, we don't expect everyone will want to use the exact malloc implementation provided here, but tools and libraries using an ABI-compatible malloc interface will be able to interoperate regardless of which actual implementation is used.

Third, it's an example showing the use of the WASI API. The libc functionality is implemented using calls to WASI functions.

Usage

The easiest way to get started with this is to use one of the prepackaged releases.

Building from source

To build a WASI sysroot from source, obtain a WebAssembly-supporting C compiler (currently this is only clang 8+, though we'd like to support other compilers as well), and then run:

make WASM_CC=/path/to/clang/with/wasm/support \
     WASM_AR=/path/to/llvm-ar \
     WASM_NM=/path/to/llvm-nm

This makes a directory called "sysroot", by default. See the top of the Makefile for customization options.

To use the sysroot, use the --sysroot= option:

/path/to/wasm/supporting/c/compiler --sysroot=/path/to/the/newly/built/sysroot ...

to run the compiler using the newly built sysroot.