Skip to content

Commit cee1bb9

Browse files
committed
The README says how to build it and how a consumer selects it
1 parent cb2e9b9 commit cee1bb9

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

README.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,28 @@ The exported surface is checked against the specification's own `SURFACE.txt`:
109109
86 names, twelve complete groups, three absent groups, and nothing beginning
110110
with `kal_` that the specification does not name.
111111

112+
## Building it, and what it needs
113+
114+
```bash
115+
mcpp build --target wasm32-emscripten
116+
```
117+
118+
Nothing has to be declared. The `wasm32-emscripten` row names its own payload
119+
(`emsdk@6.0.9`), the payload brings its own sysroot and its own libc++ module
120+
surface, and `mcpp run --target wasm32-emscripten` executes the module with
121+
`node`.
122+
123+
A consumer selects this implementation by platform and names no
124+
implementation in its source:
125+
126+
```toml
127+
[dependencies]
128+
openkal = "0.12.0"
129+
130+
[target.'cfg(os = "emscripten")'.dependencies]
131+
openkal-emscripten = "0.1.0"
132+
```
133+
112134
## Licence
113135

114136
Apache-2.0.

0 commit comments

Comments
 (0)