Daniel Samson
be04ebe954
The module-to-domain table in build-support duplicated what each domain's build.zig already states with its addModule exports. userBinary now resolves each named import by searching the packages the binary declared in its own build.zig.zon (b.available_deps), which also makes the zon the literal include path: an import can only be satisfied by a domain the binary claims, and naming a module whose domain is missing fails the build graph with the domain to declare. build-support is down to the recipe alone. All build variants green; manifest unchanged.
21 lines
779 B
Zig
21 lines
779 B
Zig
//! The fdt service as a binary package (docs/build-packages-plan.md):
|
|
//! this file names the binary and EXACTLY the modules its source imports —
|
|
//! build-support resolves each name from the domains this zon declares.
|
|
//!
|
|
//! The artifact is named "discovery" like acpi's: the Raspberry Pis hand over
|
|
//! a flattened device tree, and the aarch64 target flips the root's
|
|
//! -Ddiscovery default when it lands (docs/arm.md). A placeholder until the
|
|
//! ARM bring-up.
|
|
|
|
const std = @import("std");
|
|
const build_support = @import("build-support");
|
|
|
|
pub fn build(b: *std.Build) void {
|
|
const exe = build_support.userBinary(b, .{
|
|
.name = "discovery",
|
|
.root_source_file = b.path("fdt.zig"),
|
|
.imports = &.{ "process" },
|
|
});
|
|
b.installArtifact(exe);
|
|
}
|