From cec45b7e437adde113fa7ca0588caa16ff0935c9 Mon Sep 17 00:00:00 2001 From: Adam Langley Date: Mon, 31 Oct 2016 11:10:55 -0700 Subject: [PATCH] Update links to Bazel's site. Bazel has moved their primary site to bazel.build. (Thanks to Damien Martin-guillerez for the change.) Change-Id: Ifb29dbb79f1e1d9611f40992a3e75e0fb5a3722a Reviewed-on: https://boringssl-review.googlesource.com/11961 Reviewed-by: David Benjamin --- INCORPORATING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/INCORPORATING.md b/INCORPORATING.md index 38e9d793..6dc7fa9e 100644 --- a/INCORPORATING.md +++ b/INCORPORATING.md @@ -5,7 +5,7 @@ ## Bazel -If you are using [Bazel](http://www.bazel.io) then you can incorporate +If you are using [Bazel](https://bazel.build) then you can incorporate BoringSSL as an external repository by using a commit from the `master-with-bazel` branch. That branch is maintained by a bot from `master` and includes the needed generated files and a top-level BUILD file. @@ -38,7 +38,7 @@ updating things more complex. BoringSSL is designed to work with many different build systems. Currently, different projects use [GYP](https://gyp.gsrc.io/), [GN](https://chromium.googlesource.com/chromium/src/+/master/tools/gn/docs/quick_start.md), -[Bazel](http://bazel.io/) and [Make](https://www.gnu.org/software/make/) to +[Bazel](https://bazel.build/) and [Make](https://www.gnu.org/software/make/) to build BoringSSL, without too much pain. The development build system is CMake and the CMake build knows how to