| commit | 7662e58e3e0f6b6bcfd6e93ef8c83062096f22e2 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed May 15 16:23:12 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 16 00:27:35 2024 +0000 |
| tree | fa6903c4b33b1de4689bb7ba769f9dcf3c981649 | |
| parent | 0355048ce0302fdeb4744dae4b8a156a38496150 [diff] |
Re-add a way to run embed_test_data.go for now Android have a lot of build systems and we have not yet managed to wrangle all of them to just consume the test data directly. (Apparently passing test data to tests is a great unsolved problem in computer science.) Since this is mostly a backup mechanism now, and we don't want to apply this to *all* Android's builds, this flag works differently from before. Now it just drops crypto_test_data.cc somewhere. It is the caller's responsibility to link this into crypto_test and also build test_support with -DBORINGSSL_CUSTOM_GET_TEST_DATA. Bug: 542 Change-Id: I7faad4fa80dfacfdadd533b3cd7de95bf9e258d4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68468 Commit-Queue: David Benjamin <davidben@google.com> 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.
Project links:
There are other files in this directory which might be helpful: