-
Notifications
You must be signed in to change notification settings - Fork 70
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
Avoid passing both the short and the long proto paths to protoc #58
Comments
More context in bazelbuild/bazel#4544. |
Ping for this bug. I'm importing protobuf code to //third_party/protobuf, but the proto_library rule [1] fails to build. Adding proto_source_root="third_party/protobuf" doesn't fix the build. The failing command is:
I think the The command below works with or without
[1] https://github.com/protocolbuffers/protobuf/blob/master/BUILD#L264 |
Changed to P3 because I'm not planning to work on this next quarter. |
A lot has changed since 2018 (e.g. the aforementioned There's also work going on to change how |
Fixed in bazelbuild/bazel#10939 |
Currently for each
.proto
file Bazel passes toprotoc
the path relative to the workspace (the long path) via-I
flag (alias for--proto_path
).Since 15a4362, Bazel also passes to
protoc
a short path via the--proto_path
flag. The short path is only passed forproto_library
targets that have setproto_source_root
.Passing to
protoc
both the short and the long path to a.proto
file is error prone. A better mechanism must be implemented to deal with these situations.The text was updated successfully, but these errors were encountered: