Skip to content

Commit bc9013e

Browse files
committed
update README
1 parent e80b041 commit bc9013e

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ Add `zemscripten` and (optionally) `emsdk` to your build.zig.zon dependencies
1111

1212
Emsdk must be activated before it can be used. You can use `activateEmsdkStep` to create a build step for that:
1313
```zig
14-
const activate_emsdk_step = @import("zemscripten").activateEmsdkStep(b);
14+
const emsdk_dep = b.dependency("emsdk", .{});
15+
const activate_emsdk_step = @import("zemscripten").activateEmsdkStep(b, emsdk_dep);
1516
```
1617

1718
Add zemscripten's "root" module to your wasm compile target., then create an `emcc` build step. We use zemscripten's default flags and settings which can be overridden for your project specific requirements. Refer to the [emcc documentation](https://emscripten.org/docs/tools_reference/emcc.html). Example build.zig code:
@@ -39,6 +40,7 @@ Add zemscripten's "root" module to your wasm compile target., then create an `em
3940
4041
const emcc_step = @import("zemscripten").emccStep(
4142
b,
43+
emsdk_dep,
4244
&.{ }, // src file paths
4345
&.{ wasm }, // src compile steps
4446
.{
@@ -83,6 +85,7 @@ You can also define a run step that invokes `emrun`. This will serve the html lo
8385
const emrun_args = .{};
8486
const emrun_step = @import("zemscripten").emrunStep(
8587
b,
88+
emsdk_dep,
8689
b.getInstallPath(.{ .custom = "web" }, html_filename),
8790
&emrun_args,
8891
);

0 commit comments

Comments
 (0)