Skip to content

Generate dummy C input in Zig#2804

Draft
plajjan wants to merge 1 commit into
mainfrom
zig-dummy-c-input
Draft

Generate dummy C input in Zig#2804
plajjan wants to merge 1 commit into
mainfrom
zig-dummy-c-input

Conversation

@plajjan
Copy link
Copy Markdown
Contributor

@plajjan plajjan commented May 25, 2026

Empty selected-module sets still need a C compilation unit so Zig can produce an ActonProject artifact for a dependency.

The previous fallback wrote out/types/acton_empty.c as a build-script side effect, then passed it back to Zig as an ordinary source path. That path has no Acton source module and no Zig producer step, so a stale or pruned copy can disappear before Zig hashes the input.

Use addWriteFiles to make the fallback a generated Zig input instead. The dummy file is now produced by the Zig build graph and is no longer materialized in dependency out/types.

Empty selected-module sets still need a C compilation unit so Zig can
produce an ActonProject artifact for a dependency.

The previous fallback wrote out/types/acton_empty.c as a build-script
side effect, then passed it back to Zig as an ordinary source path.
That path has no Acton source module and no Zig producer step, so a
stale or pruned copy can disappear before Zig hashes the input.

Use addWriteFiles to make the fallback a generated Zig input instead.
The dummy file is now produced by the Zig build graph and is no longer
materialized in dependency out/types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant