Google Git
Sign in
boringssl / boringssl / e127aec9f1f481d193b8805e79c607f7666a1d6b
commite127aec9f1f481d193b8805e79c607f7666a1d6b[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sun Dec 07 12:53:46 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Dec 07 17:38:34 2025 -0800
tree3202d7d5917602a76d24faf1220a7f8e04a4e216
parent4ccf02901a217afd0fc07e9719b22bca564f362d [diff]
Don't build third-party deps with our warnings

While this has resulted in some useful patches to upstream to googletest
and google/benchmark, it's not the best use of time, and sometimes makes
updating dependencies difficult. Instead, move the warnings a little
lower.

As part of this, split up our meaningful flags from the warnings and
keep the former global for now. We probably should rework these to be
"modern CMake", but for now just order things appropriately.

Bug: 389897612
Change-Id: I367c6cc6fa7336494f813b0c083f1fab769152d1
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85247
Commit-Queue: Xiangfei Ding <xfding@google.com>
Reviewed-by: Xiangfei Ding <xfding@google.com>
1 file changed
tree: 3202d7d5917602a76d24faf1220a7f8e04a4e216
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .clang-format-ignore
  22. .gitignore
  23. API-CONVENTIONS.md
  24. AUTHORS
  25. BREAKING-CHANGES.md
  26. BUILD.bazel
  27. build.json
  28. BUILDING.md
  29. CMakeLists.txt
  30. codereview.settings
  31. CONTRIBUTING.md
  32. FUZZING.md
  33. go.mod
  34. go.sum
  35. INCORPORATING.md
  36. LICENSE
  37. MODULE.bazel
  38. MODULE.bazel.lock
  39. PORTING.md
  40. PRESUBMIT.py
  41. PrivacyInfo.xcprivacy
  42. README.md
  43. SANDBOXING.md
  44. STYLE.md
README.md

BoringSSL

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: