| commit | dcba84922c7e2881f7051c85fb5a40165ff29933 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Mar 18 17:56:44 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 18 22:27:22 2022 +0000 |
| tree | 760ec1b5cc5b8bb026bee8df1f00f4fc566d197d | |
| parent | 6378c47cb74b7b3aa696c67e5d2a17221ff5e610 [diff] |
Add vs2019 to vs_toolchain.py. VS2015 has finally dropped off our support window. As part of dropping it from the bots, I'm thinking of using the current vs2017 builders to test vs2019. In preparation for that, add a vs2019 hash to vs_toolchain.py. Change-Id: I4c3dde2825f57c39a8da0e155e96d08550d39893 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52005 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: