Skip to content

Replace the deprecated C++ compiler marker with None - #808

Open
dzbarsky wants to merge 2 commits into
bazelbuild:mainfrom
dzbarsky:codex/starlarkify-compiler-presence-marker
Open

Replace the deprecated C++ compiler marker with None#808
dzbarsky wants to merge 2 commits into
bazelbuild:mainfrom
dzbarsky:codex/starlarkify-compiler-presence-marker

Conversation

@dzbarsky

@dzbarsky dzbarsky commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Replace the Java-backed cc_common.do_not_use_tools_cpp_compiler_present marker with its existing Starlark value, None. Bazel declares the deprecated marker as a Java void struct field, so preserving the exported field with None removes the Java dependency without changing compatibility.

Validation: buildifier -mode=check and 24 passing //tests/cc/common:cc_common_tests cases.

@dzbarsky
dzbarsky marked this pull request as ready for review July 31, 2026 18:23

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.

Don't think we need to test for this.

Also; it appears we have a few (<5) files still checking this; should clean them up first.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Are these internal usages? I didn't see them in this repo. (I did see https://github.com/protocolbuffers/protobuf/blob/b790ca9a4b222070d1d7cdf93c980ddeae8a55aa/build_defs/compiler_config_setting.bzl#L5-L25 and things like that but I think they will continue to work as they did, even with the None-valued attr?)

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.

2 participants