gertvdijk
commented
4 years ago This quick-'n-dirty patch allowed me to build at least the jars. Doesn't look like the most stable change, but I'll just leave it here for reference.
--- bazel/protobuf.bzl
+++ bazel/protobuf.bzl
@@ -5,6 +5,9 @@ def _proto_path(proto):
The proto path is not really a file path
It's the path to the proto that was seen when the descriptor file was generated.
"""
+ if is_in_virtual_imports(proto):
+ return _strip_virtual_import(proto.path)
+
path = proto.path
root = proto.root.path
ws = proto.owner.workspace_root
@@ -18,6 +21,11 @@ def _proto_path(proto):
path = path[1:]
return path
+def _strip_virtual_import(path):
+ pos = path.find(_VIRTUAL_IMPORTS)
+ path = path[pos + len(_VIRTUAL_IMPORTS):]
+ return path.split("/", 1)[-1]
+
def _protoc_cc_output_files(proto_file_sources):
cc_hdrs = []
cc_srcs = []
@@ -298,3 +306,21 @@ python_proto_gen_validate = rule(
output_to_genfiles = True,
implementation = _protoc_gen_validate_python_impl,
)
+
+# From https://github.com/grpc/grpc/blob/2e7d6b94eaf6b0e11add27606b4fe3d0b7216154/bazel/protobuf.bzl:
+
+_VIRTUAL_IMPORTS = "/_virtual_imports/"
+
+def is_in_virtual_imports(source_file, virtual_folder = _VIRTUAL_IMPORTS):
+ """Determines if source_file is virtual (is placed in _virtual_imports
+ subdirectory). The output of all proto_library targets which use
+ import_prefix and/or strip_import_prefix arguments is placed under
+ _virtual_imports directory.
+ Args:
+ source_file: A proto file.
+ virtual_folder: The virtual folder name (is set to "_virtual_imports"
+ by default)
+ Returns:
+ True if source_file is located under _virtual_imports, False otherwise.
+ """
+ return not source_file.is_source and virtual_folder in source_file.path
gattytto
stale[bot]
Kernald
(This is a quick report, I can make a minimal example some time later.)
Has anybody tried to use the combination of:
protoc-gen-validate's pgv Bazel rules?I'm having issues with (at least) the build of the java_proto_gen_validate srcjars.
with sandbox debugging I see protoc invocations that explain this error:
Having a look at the argument
is not helping to make
google/protobuf/timestamp.protoimportable...I believe https://github.com/bazelbuild/bazel/issues/9215 is the cause for this and the Bazel rules require updates, similar to adjustments made in e.g. https://github.com/bazelbuild/rules_swift/pull/298.