|author||Daniel Wagner-Hall <firstname.lastname@example.org>||Mon Oct 16 20:58:08 2017 +0100|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Oct 23 18:16:27 2017 +0000|
Specify -stdlib=libc++ if APPLE If you specify any --target which refers to a x86_64-apple-darwin triple, or a more specific variant derived from it, specifying -stdlib=libc++ is required, otherwise clang falls back to libstdc++ which didn't include c++11, and fails to compile in very obscure ways (simply failing to find any c++11 symbols). Change-Id: I58025cea91eaa0c16d9b5831f9965889b75bbc31 Reviewed-on: https://boringssl-review.googlesource.com/21984 Reviewed-by: David Benjamin <email@example.com> Commit-Queue: David Benjamin <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: