You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Revise the recommended bazel version in README.md
* Add a disclaimer in the README for protobuf C++ minimum version
* Add more detail to bzlmod rules_android setup in the release notes.
PiperOrigin-RevId: 793810183
Change-Id: I6b5fbf3e7c24f7be7d7e87506dfd6b11d86a2d31
Copy file name to clipboardExpand all lines: README.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,16 @@
2
2
3
3
## Disclaimer
4
4
5
-
NOTE: This branch is a development preview of the Starlark implementation of Android rules for Bazel. This code is incomplete and may not function as-is.
5
+
NOTE: This branch is a development preview of the Starlark implementation of
6
+
Android rules for Bazel. This code is incomplete and may not function as-is.
6
7
7
-
A version of Bazel built at or near head or a recent pre-release and the following flags are necessary to use these rules:
8
+
A recent version of Bazel (7.4+, 8.0+, HEAD, Bazel 9 pre-release) is required.
8
9
9
-
```
10
-
--experimental_enable_android_migration_apis
11
-
--experimental_google_legacy_api
12
-
```
10
+
This ruleset depends on [Protobuf](https://github.com/protocolbuffers/protobuf),
11
+
which has a minimum C++ language level of 17 (as of Protobuf v30, ~2025 Q3).
12
+
Depending on your system's compiler version, you may have to set `-std=c++17`
13
+
in your C++ toolchain arguments. This repository's .bazelrc file provides a
14
+
minimal set of Bazel configuration flags to build an Android app.
0 commit comments