ci: validate every member with mcpp 2026.9.26.2 - #470
Merged
Merged
Conversation
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
Validate every member with mcpp 2026.9.26.2, released today from mcpp-community/mcpp#702 (issues #699, #701, #703).
What the release changes that a member's build can see:
directorynames the directory the compiler runs in;ldflags,mcpp::link_flag) are read as words, so a$ORIGINreaches the linker as written;mcpp::runtime_search_dirand theprepareaction role, and an action role outsidesource,check,object,artifactandprepareis refused;Searched before the release: no descriptor here escapes a link flag for the shell or ninja by hand, and the build programs under
tests/examplesuse only thesourcerole. This raise measures that on every member and platform.index.tomlmin_mcppand the openkal pins do not move: no descriptor grammar changed.