| commit | 92859cc7484ac178e77825ccb86f95edcf0b6c49 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Feb 27 12:37:19 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 27 20:26:30 2023 +0000 |
| tree | 417e162d09321a927defa568fb5631c21aae18b3 | |
| parent | 8c4ec3b7b0d69649c04778a39eed5cdca338c1c0 [diff] |
Fix the generated CMake build This fixes two issues introduced in 0e68520eb27b1f37038e9d0772cfee1d015b50c3. First, libssl never had a dependency on libcrypto, so the include directory did not get passed along. Second, although this build (unlike the other CMake build) doesn't define an install target, gRPC includes it and then pulls it into its own install target. That then runs afoul of CMake's check against include directories in install targets. To avoid this, condition the src/include directory on $<BUILD_INTERFACE:...> but omit a corresponding $<INSTALL_INTERFACE:...>. Since we're not the ones providing an install target, we don't actually know the value to use. Per [0], using the generator expression means we need to manually make it absolute ourselves. [0] https://cmake.org/cmake/help/latest/command/target_include_directories.html Change-Id: I2a25cc8382116c5957d94f65641220559b7af87d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57685 Reviewed-by: Bob Beck <bbe@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@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: