old_mixer_repo
old_mixer_repo copied to clipboard
Fix relative imports in //BUILD.api
go_proto_library(
name = "istio/config/v1",
imports = [
"../../external/com_github_google_protobuf/src"
prior comments:
geeknoid: Definitely not the right way to do this. I think the importmap feature is what you need here.
douglas-reid: importmap isn't needed for "well-known" protos. but you do need to specify where to find the sources for imports.
geeknoid: This can't be the right way to find these files. This is assuming the structure of the blaze output directories.
It most definitely exploits knowledge of bazel's build structure to accomplish its goal. I'll take another look at some point, but I believe when setting this up I tried the "obvious" workarounds and this was the only way that seemed to work.
BTW, there is a PR that is out (and has been for awhile) to the pubref repo that would fix this issue. Perhaps we should start voting for its inclusion.
How are we doing on this front? Any chance this will be addressed in 0.3? If not, let's just move the item to a different milestone.
no changes recently. although, any changes to the repo structure for the project may alter the impact of this issue.