commit | 81a6f6d8de908e27901f5c968c576fbb9c3f35d0 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu May 31 14:58:52 2018 -0400 |
committer | David Benjamin <davidben@google.com> | Thu May 31 19:02:43 2018 +0000 |
tree | c15013f36fb014de856a43e06ace65a56dd519de | |
parent | fe7a17440fe7560511615c6bd59d299a0e5d45a4 [diff] |
Add a tool to check for filename collisions. GN does not like multiple files in the same target that share a name, so add a script to check for this. A follow-up changes will hook that up to the builders, so we'll flag this in try jobs rather than when the change trickles downstream. Change-Id: Ic413dd9aeed6da54fc85dea07f80fe7084be9e9e Reviewed-on: https://boringssl-review.googlesource.com/28844 Reviewed-by: Adam Langley <agl@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: