kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update links to Bazel's site.

Browse Source 
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 <davidben@google.com>
This commit is contained in:
Adam Langley 2016-10-31 11:10:55 -07:00 committed by David Benjamin
parent 4b0d0e4c5e
commit cec45b7e43
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
INCORPORATING.md
View File

@ -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