Go to file
Dan Gohman a94d2d04e7
Avoid varargs conventions when calling open (#126)
* Add an entrypoint for calling open that bypasses the varargs.

* Add an entrypoint for calling openat that bypasses the varargs.
2019-11-04 16:37:45 -08:00
basics Avoid using user identifiers in function declarations. (#124) 2019-10-28 11:08:12 -07:00
dlmalloc Remove -fno-builtin. (#104) 2019-10-11 05:07:34 -07:00
expected/wasm32-wasi Avoid varargs conventions when calling open (#126) 2019-11-04 16:37:45 -08:00
libc-bottom-half Avoid varargs conventions when calling open (#126) 2019-11-04 16:37:45 -08:00
libc-top-half Avoid varargs conventions when calling open (#126) 2019-11-04 16:37:45 -08:00
.azure-pipelines.yml Workaround a bug causing Windows CI failures. (#119) 2019-10-22 08:00:48 -07: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 Revamp and simplify the libpreopen code. (#110) 2019-11-04 14:56:35 -08: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.