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. |
||
|---|---|---|
| .. | ||
| build.zig | ||
| build.zig.zon | ||
| bulk-only-transport.zig | ||
| scsi.zig | ||
| usb-storage.zig | ||