tensorflow: Bazel problem when using Tensorflow as an external dependency.
When using the HEAD version of Tensorflow as an external Bazel dependency (like tensorflow_serving does), we run into an issue in the line:
load("@//third_party:common.bzl", "template_rule")
inside
tensorflow/third_party/jpeg/jpeg.BUILD
That line assumes that Tensorflow is the main repository. But when Tensorflow is included in another project the main repository is the main project so that common.bzl file is not found. I think that line needs to read:
load("@org_tensorflow//third_party:common.bzl", "template_rule")
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 4
- Comments: 29 (21 by maintainers)
Commits related to this issue
- Update jpeg.BUILD Fixes #6706 — committed to yaroslavvb/tensorflow by yaroslavvb 7 years ago
I don’t think we have an issue for that, but we’re working on it. You can see that we’ve moved some code in configure to just modifying --action_env already. Once that’s all it does, you don’t have to run it any more. Still WIP.
Is there a bug to track the being able to include tensorflow in your project without having to run ./configure?
Can you please rollback the breaking change until Bazel is fixed? Today the nasm library URL broke and there is no commit that both has all the working urls and a working BUILD rule for jpeg.