mirror of
https://github.com/vale981/ray
synced 2025-03-05 10:01:43 -05:00

Bazel has a rule for enforcing the version so we can just reuse that. This redundant bazel version check logic in setup.py is also causing issue when building conda package, because conda has its own version of bazel and it doesn't support `--version`.
22 lines
690 B
Text
22 lines
690 B
Text
workspace(name = "com_github_ray_project_ray")
|
|
|
|
load("//bazel:ray_deps_setup.bzl", "ray_deps_setup")
|
|
|
|
ray_deps_setup()
|
|
|
|
load("//bazel:ray_deps_build_all.bzl", "ray_deps_build_all")
|
|
|
|
ray_deps_build_all()
|
|
|
|
# This needs to be run after grpc_deps() in ray_deps_build_all() to make
|
|
# sure all the packages loaded by grpc_deps() are available. However a
|
|
# load() statement cannot be in a function so we put it here.
|
|
load("@com_github_grpc_grpc//bazel:grpc_extra_deps.bzl", "grpc_extra_deps")
|
|
|
|
grpc_extra_deps()
|
|
|
|
load("@bazel_skylib//lib:versions.bzl", "versions")
|
|
|
|
# When the bazel version is updated, make sure to update it
|
|
# in setup.py as well.
|
|
versions.check(minimum_bazel_version = "4.2.1")
|