Repository navigation
Conversation
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix sysroot filegroup generation for Bazel builds
Expose sysroots as single directory artifacts
Oct 15, 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
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.
Bazel 9 warns because each sysroot expands into ~5,600 inputs. A single source-directory artifact gives compile actions one sandbox symlink and one merkle-tree node.
sysroot/, prune:-named and.plentries, and exposesrcs = ["."]through the existing root:sysrootalias.:headers,:libs, and:toolchain_sysrootvia subpackage forwarding. Keep archive selection and hashes unchanged.//:usr/include/stdio.hbecomes//sysroot:usr/include/stdio.h—including Envoy’s Rust SDK consumer. Add regression coverage for both Linux architectures and the empty macOS fallback.