|author||David Benjamin <firstname.lastname@example.org>||Fri Oct 27 10:43:15 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Fri Oct 27 18:58:08 2017 +0000|
Disable macOS architecture hack on CMake 3.0. Per the comment, it's no longer necessary. macOS i386 does not exist, but apparently iOS i386 does! We can probably just remove it altogether, but our cmake_minimum_required is nominally 2.8, so I just put the version check in. Bug: 210 Change-Id: I6e0617a3f292a218b2465eee85bd4814bd0e55c7 Reviewed-on: https://boringssl-review.googlesource.com/22304 Commit-Queue: Steven Valdez <email@example.com> Reviewed-by: Steven Valdez <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org>
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: