Inject the custom libc++ globally
Although modern CMake dictates that such things should flow
target-by-target, this dependency actually needs to be injected
everywhere, as if it were a toolchain. Use the link_libraries directive,
which pairs with the global add_compile_options("-nostdinc++").
This gets us part of the way to making google/benchmark work with
USE_CUSTOM_LIBCXX.
Bug: 383769319
Change-Id: Ic6c3dd817827cf1f9f4643f347ad291d388c3c2a
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85228
Commit-Queue: Xiangfei Ding <xfding@google.com>
Reviewed-by: Xiangfei Ding <xfding@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: