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
For Bazel 7.4.1, Bazel uses precompiled binary when protobuf=v26.0 or v28.3, but not for v29.0...v29.3 as I mentioned above.
For Bazel 8.0.1, Bazel starts compiling protoc for both protobuf=v26.0 and v29.0.
Thus I'm guessing that proto_library being migrated from Bazel to starlark has something to do with this.
I wasn't able to reproduce this behavior for simpler targets like @protobuf//:any_proto or @googleapis//google/type:calendar_period_proto
The text was updated successfully, but these errors were encountered:
tsawada
changed the title
proto_library: Bazel does not use precompiled toolchain since v29.0
proto_library: Bazel does not use toolchain since v29.0
Jan 31, 2025
My MODULE.bazel
.bazelrc
I use Bazel 7.4.1
With Protobuf v26.0 .. v28.3, proto_library uses prebuilt toolchain and the build finishes instantly.
With protobuf >= v29.0 by uncommenting the single_version_override line at the bottom, bazel starts compiling protoc
For Bazel 7.4.1, Bazel uses precompiled binary when protobuf=v26.0 or v28.3, but not for v29.0...v29.3 as I mentioned above.
For Bazel 8.0.1, Bazel starts compiling protoc for both protobuf=v26.0 and v29.0.
Thus I'm guessing that
proto_library
being migrated from Bazel to starlark has something to do with this.I wasn't able to reproduce this behavior for simpler targets like
@protobuf//:any_proto
or@googleapis//google/type:calendar_period_proto
The text was updated successfully, but these errors were encountered: