Skip to content

Support --incompatible_exclude_starlark_flags_from_exec_config.#4056

Open
slackito wants to merge 1 commit into
bazelbuild:mainfrom
slackito:exclude_starlark_flags_from_exec_config
Open

Support --incompatible_exclude_starlark_flags_from_exec_config.#4056
slackito wants to merge 1 commit into
bazelbuild:mainfrom
slackito:exclude_starlark_flags_from_exec_config

Conversation

@slackito
Copy link
Copy Markdown
Collaborator

This change adds scope = "universal" to some settings that need to be preserved in exec config.

@slackito slackito requested review from krasimirgg and scentini May 21, 2026 17:08
@slackito slackito force-pushed the exclude_starlark_flags_from_exec_config branch from 1356f36 to c694d74 Compare May 28, 2026 10:13
rust_toolchain_channel_flag = rule(
doc = "A build setting which represents the Rust toolchain channel. The allowed values are {}".format(_CHANNELS),
implementation = _rust_toolchain_channel_flag_impl,
attrs = {"scope": attr.string(default = "universal")},
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not super familiar with this flag, this sounds OK but just tagging -- @UebelAndre to double-check -- idea is that if we're using say nightly for the target platform, we should be also using nightly for the exec one at least for consistently with proc-macros I think?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense. We really want the same toolchain to be used when switching between rlib and proc macro outputs (obviously transitioning the target platform) so for now this makes the most sense to me :)

This change adds `scope = "universal"` to some settings that need
to be preserved in exec config.
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.

3 participants