Skip to content

Add strip_level_select for per-target stripping - #4167

Open
nmattia wants to merge 1 commit into
bazelbuild:mainfrom
nmattia:nm-strip-level-select
Open

Add strip_level_select for per-target stripping#4167
nmattia wants to merge 1 commit into
bazelbuild:mainfrom
nmattia:nm-strip-level-select

Conversation

@nmattia

@nmattia nmattia commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Closes #3730

This adds a new tag class, strip_level_select, which allows specifying the strip level for a collection of triples (inspired by annotation_select in the crate extension).

@nmattia

nmattia commented Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

@illicitonion I wasn't sure about the exact semantics of strip_level = None when registering the toolchains, and I'm not 100% sure what it expects (should all triples be listed?). Let me know your thoughts!

Closes bazelbuild#3730

This adds a new tag class, `strip_level_select`, which allows specifying
the strip level for a collection of triples (inspired by
`annotation_select` in the `crate` extension).
@nmattia
nmattia force-pushed the nm-strip-level-select branch from f23049b to f8f382c Compare July 24, 2026 12:27
pull Bot pushed a commit to bit-cook/ic that referenced this pull request Jul 27, 2026
This drops our local rules_rust patch which we used to hardcode strip
values, and instead use the new `strip_level_select` tag:

bazelbuild/rules_rust#4167
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot specify per-target strip_level in MODULE.bazel

1 participant