-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove native Protobuf rules #10005
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
team-Rules-Server
Issues for serverside rules included with Bazel
type: feature request
Comments
Yannic
added a commit
to Yannic/rules_proto_bazelbuild
that referenced
this issue
Oct 13, 2019
This was referenced Oct 13, 2019
Closed
jin
added
team-Rules-Server
Issues for serverside rules included with Bazel
untriaged
labels
Oct 14, 2019
cc @lberki |
hlopko
added
P2
We'll consider working on this in future. (Assignee optional)
type: feature request
and removed
untriaged
labels
Oct 28, 2019
Yannic
added a commit
to Yannic/rules_proto_bazelbuild
that referenced
this issue
Dec 18, 2019
Yannic
added a commit
to Yannic/rules_proto_bazelbuild
that referenced
this issue
Dec 18, 2019
Yannic
added a commit
to Yannic/rules_proto_bazelbuild
that referenced
this issue
Dec 18, 2019
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
This change adds a new `proto_toolchain` rule which we will use later to resolve tools and options required to compile Protocol Buffers, thus eventually replacing some of the command-line options from `ProtoConfiguration`. To preclude inconsistencies in the migration period, we will start with a `proto_toolchain` rule that doesn't have any arguments and populate its provider from the existing command-line options. After all consumers have been migrated to resolve the tools from the toolchain instead of reading the command-line, we will replace all proto-specific flags with attributes on `proto_toolchain` (or similar, language-specific toolchains for flags that only affect a specific language). Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
This change adds a new `proto_toolchain` rule which we will use later to resolve tools and options required to compile Protocol Buffers, thus eventually replacing some of the command-line options from `ProtoConfiguration`. To preclude inconsistencies in the migration period, we will start with a `proto_toolchain` rule that doesn't have any arguments and populate its provider from the existing command-line options. After all consumers have been migrated to resolve the tools from the toolchain instead of reading the command-line, we will replace all proto-specific flags with attributes on `proto_toolchain` (or similar, language-specific toolchains for flags that only affect a specific language). Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
This change adds a new `proto_toolchain` rule which we will use later to resolve tools and options required to compile Protocol Buffers, thus eventually replacing some of the command-line options from `ProtoConfiguration`. To preclude inconsistencies in the migration period, we will start with a `proto_toolchain` rule that doesn't have any arguments and populate its provider from the existing command-line options. After all consumers have been migrated to resolve the tools from the toolchain instead of reading the command-line, we will replace all proto-specific flags with attributes on `proto_toolchain` (or similar, language-specific toolchains for flags that only affect a specific language). Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
This change adds a new `proto_toolchain` rule which we will use later to resolve tools and options required to compile Protocol Buffers, thus eventually replacing some of the command-line options from `ProtoConfiguration`. To preclude inconsistencies in the migration period, we will start with a `proto_toolchain` rule that doesn't have any arguments and populate its provider from the existing command-line options. After all consumers have been migrated to resolve the tools from the toolchain instead of reading the command-line, we will replace all proto-specific flags with attributes on `proto_toolchain` (or similar, language-specific toolchains for flags that only affect a specific language). Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
This change adds a new `proto_toolchain` rule which we will use later to resolve tools and options required to compile Protocol Buffers, thus eventually replacing some of the command-line options from `ProtoConfiguration`. To preclude inconsistencies in the migration period, we will start with a `proto_toolchain` rule that doesn't have any arguments and populate its provider from the existing command-line options. After all consumers have been migrated to resolve the tools from the toolchain instead of reading the command-line, we will replace all proto-specific flags with attributes on `proto_toolchain` (or similar, language-specific toolchains for flags that only affect a specific language). Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
This change adds a new `proto_toolchain` rule which we will use later to resolve tools and options required to compile Protocol Buffers, thus eventually replacing some of the command-line options from `ProtoConfiguration`. To preclude inconsistencies in the migration period, we will start with a `proto_toolchain` rule that doesn't have any arguments and populate its provider from the existing command-line options. After all consumers have been migrated to resolve the tools from the toolchain instead of reading the command-line, we will replace all proto-specific flags with attributes on `proto_toolchain` (or similar, language-specific toolchains for flags that only affect a specific language). Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
Part of the migration of Protobuf rules/aspects to `ProtoSource`. A future change will make `ProtoInfo` mandatory (similar to what was done for `proto_lang_toolchain`). Note that this is for Obj-C Protobuf rules which don't exist in Bazel. Updates bazelbuild#10005
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Nov 14, 2020
Part of the migration of Protobuf rules/aspects to `ProtoSource`. A future change will make `ProtoInfo` mandatory (similar to what was done for `proto_lang_toolchain`). Note that this is for Obj-C Protobuf rules which don't exist in Bazel. Updates bazelbuild#10005
lberki
added
P3
We're not considering working on this, but happy to review a PR. (No assignee)
and removed
P2
We'll consider working on this in future. (Assignee optional)
labels
Nov 18, 2020
Yannic
added a commit
to Yannic/bazel
that referenced
this issue
Jan 26, 2021
This change exposes the values of `--protoc` and `--proto_options` to Starlark, thus making it possible to implement `proto_toolchain` in Starlark. See bazelbuild/rules_proto#82 for the implementation of `proto_toolchain`. Working towards bazelbuild#10005
Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
team-Rules-Server
Issues for serverside rules included with Bazel
type: feature request
This is the ☔️-bug for removing the native versions of everything related to Protocol Buffers from Bazel.
Blocked on:
The text was updated successfully, but these errors were encountered: