|
| 1 | +const std = @import("std"); |
| 2 | + |
| 3 | +// Although this function looks imperative, note that its job is to |
| 4 | +// declaratively construct a build graph that will be executed by an external |
| 5 | +// runner. |
| 6 | +pub fn build(b: *std.Build) void { |
| 7 | + // Standard target options allows the person running `zig build` to choose |
| 8 | + // what target to build for. Here we do not override the defaults, which |
| 9 | + // means any target is allowed, and the default is native. Other options |
| 10 | + // for restricting supported target set are available. |
| 11 | + const target = b.standardTargetOptions(.{}); |
| 12 | + |
| 13 | + // Standard optimization options allow the person running `zig build` to select |
| 14 | + // between Debug, ReleaseSafe, ReleaseFast, and ReleaseSmall. Here we do not |
| 15 | + // set a preferred release mode, allowing the user to decide how to optimize. |
| 16 | + const optimize = b.standardOptimizeOption(.{}); |
| 17 | + |
| 18 | + // We will also create a module for our other entry point, 'main.zig'. |
| 19 | + const exe_mod = b.createModule(.{ |
| 20 | + // `root_source_file` is the Zig "entry point" of the module. If a module |
| 21 | + // only contains e.g. external object files, you can make this `null`. |
| 22 | + // In this case the main source file is merely a path, however, in more |
| 23 | + // complicated build scripts, this could be a generated file. |
| 24 | + .root_source_file = b.path("src/main.zig"), |
| 25 | + .target = target, |
| 26 | + .optimize = optimize, |
| 27 | + }); |
| 28 | + |
| 29 | + // This creates another `std.Build.Step.Compile`, but this one builds an executable |
| 30 | + // rather than a static library. |
| 31 | + const exe = b.addExecutable(.{ |
| 32 | + .name = "zig", |
| 33 | + .root_module = exe_mod, |
| 34 | + }); |
| 35 | + |
| 36 | + // This declares intent for the executable to be installed into the |
| 37 | + // standard location when the user invokes the "install" step (the default |
| 38 | + // step when running `zig build`). |
| 39 | + b.installArtifact(exe); |
| 40 | + |
| 41 | + // This *creates* a Run step in the build graph, to be executed when another |
| 42 | + // step is evaluated that depends on it. The next line below will establish |
| 43 | + // such a dependency. |
| 44 | + const run_cmd = b.addRunArtifact(exe); |
| 45 | + |
| 46 | + // By making the run step depend on the install step, it will be run from the |
| 47 | + // installation directory rather than directly from within the cache directory. |
| 48 | + // This is not necessary, however, if the application depends on other installed |
| 49 | + // files, this ensures they will be present and in the expected location. |
| 50 | + run_cmd.step.dependOn(b.getInstallStep()); |
| 51 | + |
| 52 | + // This allows the user to pass arguments to the application in the build |
| 53 | + // command itself, like this: `zig build run -- arg1 arg2 etc` |
| 54 | + if (b.args) |args| { |
| 55 | + run_cmd.addArgs(args); |
| 56 | + } |
| 57 | + |
| 58 | + // This creates a build step. It will be visible in the `zig build --help` menu, |
| 59 | + // and can be selected like this: `zig build run` |
| 60 | + // This will evaluate the `run` step rather than the default, which is "install". |
| 61 | + const run_step = b.step("run", "Run the app"); |
| 62 | + run_step.dependOn(&run_cmd.step); |
| 63 | + |
| 64 | + const exe_unit_tests = b.addTest(.{ |
| 65 | + .root_module = exe_mod, |
| 66 | + }); |
| 67 | + |
| 68 | + const run_exe_unit_tests = b.addRunArtifact(exe_unit_tests); |
| 69 | + |
| 70 | + // Similar to creating the run step earlier, this exposes a `test` step to |
| 71 | + // the `zig build --help` menu, providing a way for the user to request |
| 72 | + // running the unit tests. |
| 73 | + const test_step = b.step("test", "Run unit tests"); |
| 74 | + test_step.dependOn(&run_exe_unit_tests.step); |
| 75 | +} |
0 commit comments