Repository navigation
Add cached per-source custom rules with tracked generated artifacts - #60
Merged
Merged
Conversation
godofecht
marked this pull request as ready for review
October 17, 2026 13:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implement a scoped native analogue of CMake 4.5
add_custom_rule()using tracked per-source Zig Run actions.CustomRule/CustomRuleBindingaccept<SOURCE>,<OUTPUT>, optional tracked<GENERATOR>, andderiveoverrides; generated C/C++ sources enter compilation throughLazyPath. Preserve the existingcustom_commandspath and migrate thegenerated-codeexample to the new API.Verification
GitHub Actions CI passed on this PR head (
cee53d89): all unit-test jobs and the example matrix completed successfully on Zig 0.14.1, 0.15.2, and 0.16.0. The example matrix includesgenerated-code. CMake interop and corpus jobs also passed. No local Zig binary was available.Scope
This is intentionally not full CMake 4.5 file-set semantics: one generated source per input, no depfile/byproducts/configurators yet; custom rules currently require Zig native compilation and explicitly enabled system commands. See
docs/CUSTOM_RULES.md.