Update documentation to reference the “master-with-bazel” branch.
We now have a branch that contains the source code in a form suitable
for using with Bazel. This can be easier for projects that are already
using Bazel to deal with.
Change-Id: Iaaddb2ee50b367114ff2de88a526bf4bdb6ad7ab
Reviewed-on: https://boringssl-review.googlesource.com/8651
Reviewed-by: David Benjamin <davidben@google.com>
diff --git a/INCORPORATING.md b/INCORPORATING.md
index d53f2b5..5ab8a60 100644
--- a/INCORPORATING.md
+++ b/INCORPORATING.md
@@ -3,6 +3,24 @@
**Note**: if your target project is not a Google project then first read the
[main README](/README.md) about the purpose of BoringSSL.
+## Bazel
+
+If you are using [Bazel](http://www.bazel.io) 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.
+
+For example:
+
+ git\_repository(
+ name = "boringssl",
+ commit = "_some commit_",
+ remote = "https://boringssl.googlesource.com/boringssl",
+ )
+
+You would still need to keep the referenced commit up to date if a specific
+commit is referred to.
+
## Directory layout
Typically projects create a `third_party/boringssl` directory to put
