From f448c609035d5afb83d5de4c2b3f619f793cd832 Mon Sep 17 00:00:00 2001 From: Adam Langley Date: Tue, 17 May 2016 12:33:27 -0700 Subject: [PATCH] Update INCORPORATING.md to clarify one point. 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 --- INCORPORATING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/INCORPORATING.md b/INCORPORATING.md index 58f37db9..d53f2b52 100644 --- a/INCORPORATING.md +++ b/INCORPORATING.md @@ -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