40ec347196
Apparently Bazel has deprecated the built-in licenses() command and now expects you to pull in an external package. I think I've gotten this right? Since our new BUILD.bazel file is actually referenced by the old -with-bazel branch, this new dependency also needs to work there. That is still using the legacy WORKSPACE system, but I got that working there too, I think. However, as the legacy WORKSPACE system does not consider recursive dependencies, anyone using it and updating BoringSSL will need to, in turn, update their WORKSPACE file on update. Fixed: 365824757 Change-Id: I7b49f33d628cec2ec07a47f0e31f16765d0f532a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71147 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Ben Lawson <benlawson@google.com> Reviewed-by: Adam Langley <agl@google.com>
38 lines
1.7 KiB
Python
38 lines
1.7 KiB
Python
# Copyright (c) 2024, Google Inc.
|
|
#
|
|
# Permission to use, copy, modify, and/or distribute this software for any
|
|
# purpose with or without fee is hereby granted, provided that the above
|
|
# copyright notice and this permission notice appear in all copies.
|
|
#
|
|
# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
|
|
# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
|
|
# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
|
|
# SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
|
|
# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
|
|
# OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
|
|
# CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
|
|
|
# When publishing to BCR, replace the version field below with
|
|
# 0.0.0-YYYYMMDD-HASH, e.g. "0.0.0-20240126-22d349c".
|
|
module(
|
|
name = "boringssl",
|
|
version = "0.0.0-dev",
|
|
compatibility_level = 2,
|
|
)
|
|
|
|
# Periodically update the following dependencies to their latest versions
|
|
# listed on https://registry.bazel.build/. When doing so, run
|
|
# `bazelisk test ...` to update the hashes in MODULE.bazel.lock.
|
|
|
|
# In principle, googletest is only needed for tests and could be a
|
|
# dev_dependency. But it would then be impossible for downstream modules to run
|
|
# BoringSSL's tests. The downstream module provides the toolchain, so we may
|
|
# need to request they run tests when triaging issues. If
|
|
# https://github.com/bazelbuild/bazel/issues/22187 is ever fixed, we can change
|
|
# this.
|
|
bazel_dep(name = "googletest", version = "1.15.2")
|
|
|
|
bazel_dep(name = "platforms", version = "0.0.10")
|
|
bazel_dep(name = "rules_cc", version = "0.0.9")
|
|
bazel_dep(name = "rules_license", version = "1.0.0")
|