mirror of
https://github.com/tensorflow/tensorflow.git
synced 2024-11-21 21:05:19 +00:00
3927c6d1f5
PiperOrigin-RevId: 444765691
31 lines
1.4 KiB
Python
31 lines
1.4 KiB
Python
"""Loads pasta python package."""
|
|
|
|
load("//third_party:repo.bzl", "tf_http_archive", "tf_mirror_urls")
|
|
|
|
def repo():
|
|
tf_http_archive(
|
|
name = "pasta",
|
|
urls = tf_mirror_urls("https://github.com/google/pasta/archive/v0.2.0.tar.gz"),
|
|
strip_prefix = "pasta-0.2.0",
|
|
sha256 = "b9e3bcf5ab79986e245c8a2f3a872d14c610ce66904c4f16818342ce81cf97d2",
|
|
build_file = "//third_party/pasta:pasta.BUILD",
|
|
system_build_file = "//third_party/pasta:BUILD.system",
|
|
|
|
# We want to add a bazel macro for use in the `@pasta` BUILD file.
|
|
#
|
|
# If we have this file live in this repo, referencing it from `@pasta`
|
|
# becomes tricky. If we do `@//` the build breaks when this repo
|
|
# (TensorFlow) is *not* the main repo (i.e. when TensorFlow is used as
|
|
# a dependency in another workspace). If we hardcode `@org_tensorflow`,
|
|
# the build breaks when this repo is used in another workspace under a
|
|
# different name.
|
|
#
|
|
# We could generate `build_defs.bzl` to reference this repo by whatever
|
|
# name it's registered with. Or we could just symlink `build_defs.bzl`
|
|
# into the `@pasta` repo and then reference it with a repo relative
|
|
# label; i.e. `//:build_defs.bzl`:
|
|
link_files = {
|
|
"//third_party/pasta:build_defs.bzl": "build_defs.bzl",
|
|
},
|
|
)
|