envconfig: recognize kache as a compiler wrapper - #15997
Open
Guara92 wants to merge 1 commit into
Open
Conversation
Member
|
This needs release notes and probably some documentation around the same areas with |
eli-schwartz
requested changes
Aug 3, 2026
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
3 participants
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.
Setting a compiler wrapper meson doesn't know about, e.g.
CC="kache cc"(kache is a compiler cache), breaks Rust projects: the wrapper ends up in the compiler exelist and rust compiler detection promotes it to the linker:This teaches
parse_entryabout kache, following what #9428 did for sccache, plus adetect_kache()used to validate that the binary exists.Autodetection is deliberately not added: kache's CLI only accepts specific compiler subcommands (
kache cc,kache c++), so prepending it to arbitrary compilers wouldn't be safe.FWIW, cc-rs recently added kache to its known compiler wrappers for the same reason.