Go to file
Dan Gohman 1f40984219 Factor out the include-file exclude list into a variable.
This also starts categorizing these headers into groups and adding
comments explaining their purpose.
2019-10-07 08:59:24 -07:00
basics Add complex builtins for creal and cimag too. 2019-05-15 11:52:56 -07:00
dlmalloc Set the MALLOC_ALIGNMENT to 16. 2019-09-07 07:22:18 -07:00
expected/wasm32-wasi When checking undefined symbol list, ignore certain llvm buildins 2019-08-29 20:39:11 -07:00
libc-bottom-half Fix a warning about a spurious redundant static keyword. 2019-08-29 10:27:41 -07:00
libc-top-half Fix _DIRENT_HAVE_D_* macros. 2019-08-29 10:22:03 -07:00
.azure-pipelines.yml Add Azure Pipelines definition (#78) 2019-08-12 13:50:53 +02:00
.gitignore gitignore build 2019-04-19 11:16:25 -07:00
CODE_OF_CONDUCT.md Add a CODE_OF_CONDUCT.md file. (#101) 2019-10-03 14:15:49 +02:00
LICENSE WASI libc prototype implementation. 2019-03-27 07:59:55 -07:00
Makefile Factor out the include-file exclude list into a variable. 2019-10-07 08:59:24 -07:00
README.md Update docs to say "libc" rather than "sysroot" where applicable. 2019-08-29 10:27:23 -07:00

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.