Google Git
Sign in
boringssl / boringssl.git / 67bb28c0fe17286b0b31864e91e70b9555887e53
commit67bb28c0fe17286b0b31864e91e70b9555887e53[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Feb 01 14:40:03 2023 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Feb 01 19:51:58 2023 +0000
tree3e612cc6734f3181a50cf022b0f959bfb73dfc58
parent0a1af7828fdb929e2df27007002f5ffe7126670e [diff]
Fix OPENSSL_NO_ASM builds with the generated CMake build.

I inadverterntly broke this in
https://boringssl-review.googlesource.com/c/boringssl/+/56445

Bug: 542
Change-Id: I55dbf18314196d00f4ce19c3f59eabeccb17a8d7
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56766
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
1 file changed
tree: 3e612cc6734f3181a50cf022b0f959bfb73dfc58
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. include/
  7. rust/
  8. ssl/
  9. third_party/
  10. tool/
  11. util/
  12. .clang-format
  13. .gitignore
  14. API-CONVENTIONS.md
  15. BREAKING-CHANGES.md
  16. BUILDING.md
  17. CMakeLists.txt
  18. codereview.settings
  19. CONTRIBUTING.md
  20. FUZZING.md
  21. go.mod
  22. go.sum
  23. INCORPORATING.md
  24. LICENSE
  25. OpenSSLConfig.cmake
  26. PORTING.md
  27. README.md
  28. SANDBOXING.md
  29. sources.cmake
  30. 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:

There are other files in this directory which might be helpful: