| commit | 603e44e105d687132079ecc0219d0612118f0194 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Jul 02 16:08:05 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 02 14:14:31 2025 -0700 |
| tree | c0ae74e4b3dc5eccc5c628644afc065e07b073f8 | |
| parent | c6935ed2e643f5e24681150100dd448b01e1ce3c [diff] |
Supress the run_tests target when we're a subdirectory gRPC imports us as a subdirectory and CMake has no namespacing to speak of for that pattern. https://gitlab.kitware.com/cmake/cmake/-/issues/16414 https://gitlab.kitware.com/cmake/cmake/-/issues/22687 The run_tests target is not great in that model, both because it's unnamespaced, and because it reportedly conflicts with CTest's RUN_TESTS target, when generating MSVC projects because it's case-insensitive. Probably what we actually want is to register our tests with CTest and somehow convince CTest to behave reasonably, but for now let's just suppress it. Also namespace the all_tests helper target to avoid that leaking unhelpfully. Though really it's meant to be private helper target and not exported anywhere. We probably should similarly gate all our warning flags and other dev-specific defaults on PROJECT_IS_TOP_LEVEL, but I'll leave that for later. Bug: 428112180 Change-Id: Ib7c09c3aa083e373c97a9a5a903459b1eb7b56f4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80188 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: 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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: