| commit | c5aa8414da0e7a78f1d3865183a5c23da743c4ff | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jul 29 17:41:58 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Aug 01 18:38:22 2016 +0000 |
| tree | 21b9aaaa59839a9f1b15bd48c56bfb243daf9403 | |
| parent | 9498e74a92ce6289af2a9dddb14b75445de87d9c [diff] |
Fix up header file handling. As of a recent change, test_support always included the headers, which causes Android's new build-system to be unhappy. It doesn't want to include headers. Split them into test_support_headers and test_support to match the other keys. Then fix up references: - Android's new build system only wants the sources. Fix this. - Chromium's GN and GYP theoretically want the sources and headers, but we've never supplied the headers because this isn't enforced at all. Fix this. Headers are selected based on what target the header "belongs to". - Bazel has no change except to sort test_support_sources. Change-Id: I85809e70a71236b5e91d87f87bb73bc2ea289251 Reviewed-on: https://boringssl-review.googlesource.com/9044 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: