ci: add ccache to libuvc build check - #4
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.
What
Add bounded ccache coverage to the libuvc CMake build-check workflow and document the cache contract.
Why
The w6-6 audit found that libuvc's Ubuntu C/C++ builds had no compiler cache. The workflow now installs ccache, restores/saves only a workspace-local ccache directory, keys it by runner/compiler/source inputs, and wires both auto-detach ON/OFF CMake configurations through ccache.
How to verify
.github/workflows/build.yml.git diff --checkand the scoped diff audit pass; no tests were changed, deleted, skipped, or weakened.Risks
Only compiler-cache files are cached;
build/,build-off/, and generated artifacts are excluded. The documentation-onlyweb.ymlworkflow is unchanged.