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

Update INCORPORATING.md to clarify one point.

Browse Source 
In practice it seems that it's not clear that consumers of BoringSSL
generally check in the generated files.

Change-Id: Iaa03aa62139bbcf3e7e7f68662073854954b835f
Reviewed-on: https://boringssl-review.googlesource.com/7956
Reviewed-by: David Benjamin <davidben@google.com>
This commit is contained in:
Adam Langley 2016-05-17 12:33:27 -07:00 committed by David Benjamin
parent 4fac8d0eae
commit f448c60903
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
INCORPORATING.md
View File

@ -46,6 +46,11 @@ and
[test](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl/BUILD.generated_tests.gni)
lists generated for GN in Chromium.
Generally one checks in these generated files alongside the hand-written build
files. Periodically an engineer updates the BoringSSL revision, regenerates
these files and checks in the updated result. As an example, see how this is
done [in Chromium](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl/).
## Defines
BoringSSL does not present a lot of configurability in order to reduce the