Daniel Samson
4476208361
Every binary's build.zig now names precisely the modules its source
imports (derived by scanning each artifact's sources, transitively
through same-directory files), and its zon carries only the domains
those come from — kernel stays implicit (the root shim + link script
live there). build-support's userBinary resolves each name through one
module-to-domain table (module_homes); Domains/domains()/defaultImports
and the raw recipe entry point are deleted. An undeclared @import is a
compile error (verified: injecting @import("xkeyboard-config") into
logger fails with 'no module named ... available within module
program'), and e.g. xkeyboard-config now appears in exactly two
manifests — the two keyboard drivers. Availability never bloated the
emitted binaries (Zig compiles only what a program imports); this makes
the declared interfaces honest. Production and -Dtest-case manifests
byte-identical; all build variants and standalone package builds
green.
19 lines
711 B
Zig
19 lines
711 B
Zig
//! The device-manager service as a binary package (docs/build-packages-plan.md):
|
|
//! this file names the binary and EXACTLY the modules its source imports —
|
|
//! the shared recipe and the module-to-domain map live in build-support.
|
|
|
|
const std = @import("std");
|
|
const build_support = @import("build-support");
|
|
|
|
pub fn build(b: *std.Build) void {
|
|
const exe = build_support.userBinary(b, .{
|
|
.name = "device-manager",
|
|
.root_source_file = b.path("device-manager.zig"),
|
|
.imports = &.{
|
|
"device-manager-protocol", "device-registry", "driver", "file-system", "ipc",
|
|
"logging", "memory", "process", "service", "time",
|
|
},
|
|
});
|
|
b.installArtifact(exe);
|
|
}
|