//! init (PID 1) as a binary package (docs/build-packages-plan.md, phase 2):
//! this file names only what is specific to init — the shared recipe and the
//! default-import wiring live in build-support. The root build consumes the
//! artifact for the boot image and forwards its -Dserial here.

const std = @import("std");
const build_support = @import("build-support");

pub fn build(b: *std.Build) void {
    const exe = build_support.userBinary(b, .{
        .name = "init",
        .root_source_file = b.path("init.zig"),
        .domains = build_support.domains(b),
    });
    // init speaks the power protocol (orderly shutdown, docs/power.md) and
    // parses its boot service list from /etc/init.csv with the shared csv
    // helpers. Which services it starts is data, not a compile-time option:
    // the root build selects which init.csv variant is bundled (-Ddiagnose).
    build_support.programModule(exe).addImport("power-protocol", b.dependency("protocol", .{}).module("power-protocol"));
    build_support.programModule(exe).addImport("csv", b.dependency("csv", .{}).module("csv"));
    // init reads the same `serial` flag the kernel does: its liveness heartbeat
    // is a serial/test-build diagnostic (the QEMU harness's init tests assert
    // on it, and -Dserial images emit it), so a flashable image runs a purely
    // event-driven PID 1 that wakes only for real work. The root build forwards
    // its top-level -Dserial as this dependency option.
    const serial = b.option(bool, "serial", "Compile the serial liveness heartbeat in (forwarded from the root -Dserial)") orelse false;
    const init_options = b.addOptions();
    init_options.addOption(bool, "serial", serial);
    build_support.programModule(exe).addImport("build_options", init_options.createModule());
    b.installArtifact(exe);
}