| commit | f36c3ad3e4b7794c658a883413edb71a2e937ce1 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jan 15 12:45:57 2019 -0600 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 16 21:14:00 2019 +0000 |
| tree | 73f58f20d8df4e89303cf35bd7b3929f96aee15a | |
| parent | 5590c715e26790d9b60384e1ac092529a19208af [diff] |
Don't look for libunwind if cross-compiling. pkg-config gets confused and doesn't know to look in, say, /usr/lib/i386-linux-gnu when building for 32-bit. Fortunately, CMake sets a CMAKE_CROSSCOMPILING variable whenever CMAKE_SYSTEM_NAME is set manually (as done in util/32-bit-toolchain.cmake). Change-Id: I638b4d54ea92ade4b2b5baa40a3c5e8c17914d46 Reviewed-on: https://boringssl-review.googlesource.com/c/34305 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@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: