commit | e5d41a57e6a9e42e454ad9baf7cc3e1ab0926211 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Feb 18 17:03:26 2021 -0500 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Feb 19 16:24:54 2021 +0000 |
tree | 30aa3b2a0564edccbab467e114791c93aae03a2c | |
parent | be9a86f459f8e785bac42abcea5d13bd4ded251e [diff] |
Future-proof vs_toolchain.py for VS2019. In trying to figure out an ARM64 builder issue, I tried VS2019. That didn't fix the ARM64 issue, but it did reveal that I ported over some of the logic from Chromium wrong. For "new-style" paths, the toolchain directory should be toolchain_data['path'], not the parent directory of win_sdk. (The latest VS2019 package in Chromium puts win_sdk a few directories down from the toolchain root.) This CL should be a no-op for now because all our current toolchains use Chromium's "old-style" win_sdk-relative paths. Change-Id: I8ad7784abb479d1ede3995a44433e57448e8debf Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45744 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.
Project links:
There are other files in this directory which might be helpful: