| commit | 00e3ffb10bb07b247c8993c3e4682acd4e217ed0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jul 11 16:43:01 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 11 21:43:07 2023 +0000 |
| tree | acc1c791f41cb5caac237d2ab9c5a92b86adbd3e | |
| parent | 70be01270bd98169afaeee62f5f73243cb8764cf [diff] |
Move file_test_gtest.cc to CRYPTO_TEST_SOURCES for now file_test_gtest.cc depends on GetTestData which, for now, only exists in crypto_test because of how the crypto_test_data machinery works. Ideally that would be fixed but, for now, move the file out of test_support. Things were previously building because we were relying on the static linker to drop the file in the other targets, before the linker would notice the undefined symbol. I'm not sure what's different about Chromium, but somehow Chromium is sensitive to this. Bug: 542 Change-Id: I38c7719e7c3f27bcfeeab9693fcd43fbd0300799 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61526 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: 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: