| commit | 7c3ce519e80122fa3ba326dc0aa5c8576ccd1250 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Sep 30 18:50:26 2018 -0500 |
| committer | Adam Langley <agl@google.com> | Mon Oct 01 20:34:39 2018 +0000 |
| tree | e69b5c75e2ef38547ec816c63bb00bf8a0583c01 | |
| parent | 52483994c8f4e2861a071c20d0342970709d60a1 [diff] |
Actually disable RandTest.Fork on iOS. TARGET_OS_IPHONE isn't defined without including <TargetConditionals.h>. Oops. Confirmed now that OPENSSL_IOS gets defined where we expect. Update-Note: There is some chance this will fail to build on some macOS host builds of Android? https://codereview.chromium.org/538563002 suggests something weird happens. However those Android builds of BoringSSL would already be problematic because they'd set OPENSSL_STATIC_ARMCAP thinking they were iOS. Thus I've intentionally kept the assumption that __APPLE__ implies a Darwin target. If it goes through, all is well. If not, we'll learn more about that configuration and that we likely need to revise our OPENSSL_APPLE definition. Bug: chromium:890115 Change-Id: I1df73ac2321391d2449edbeb9cfa295fd607f935 Reviewed-on: https://boringssl-review.googlesource.com/32204 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: