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
Bazel cannot build proto_library with strip_import_prefix and multiple proto files importing each other.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
git clone git@github.com:linzhp/bazel_examples.git
cd bazel_examples
bazel build -s proto/infra:infrapb_proto
What operating system are you running Bazel on?
macOS 10.14.2
What's the output of bazel info release?
release 0.22.0
Have you found anything relevant by searching the web?
The parameter strip_import_prefix is added in #5536, but the test case does not cover the scenario when a proto_library has several proto files in the srcs importing each other.
Any other information, logs, or outputs that you want to share?
From the actual protoc command Bazel runs, we can see that the import prefix was not stripped in
Description of the problem / feature request:
Bazel cannot build
proto_library
withstrip_import_prefix
and multiple proto files importing each other.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
git clone git@github.com:linzhp/bazel_examples.git cd bazel_examples bazel build -s proto/infra:infrapb_proto
What operating system are you running Bazel on?
macOS 10.14.2
What's the output of
bazel info release
?release 0.22.0
Have you found anything relevant by searching the web?
The parameter
strip_import_prefix
is added in #5536, but the test case does not cover the scenario when aproto_library
has several proto files in thesrcs
importing each other.Any other information, logs, or outputs that you want to share?
From the actual protoc command Bazel runs, we can see that the import prefix was not stripped in
After manually removing the import prefix in
--direct_dependencies
, the protoc command would succeed.The text was updated successfully, but these errors were encountered: