| commit | feca9e562c0b7ae0ea18cfc41ec075c162751425 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Mon Jan 23 13:07:50 2017 -0800 |
| committer | Adam Langley <agl@google.com> | Mon Jan 23 21:36:37 2017 +0000 |
| tree | b3565d351b08920953bc82b8025c4ce4fc363bff | |
| parent | 8d565580310d2b175aa114b4211b24ad7e7658cc [diff] |
Emit ssl_[c|cc]_sources for Bazel. Bazel doesn't allow one to give different flags for C and C++ files, so trying to set -std=c11 for all ssl/ sources (which now include C++) blows up. This change splits the lists for Bazel so that they can be put in different cc_library targets and thus have different flags. Change-Id: I1e3dee01b6558de59246bc470527d44c9c86b188 Reviewed-on: https://boringssl-review.googlesource.com/13206 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: