Google Git
Sign in
boringssl / boringssl.git / 478b28ab12f2001a03261624261fd041f5439706
commit478b28ab12f2001a03261624261fd041f5439706[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu Nov 02 17:19:37 2023 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Nov 03 16:41:14 2023 +0000
tree088792340c46c322fcd4f1532d35e408c87be120
parentf714cb2935906a2f085c3b89d7e206af94627b56 [diff]
Fix delocate build rules with make

$CMAKE_ASM_FLAGS does not do variable expansion in CMake, only
${CMAKE_ASM_FLAGS}. As a result, we got the string "$CMAKE_ASM_FLAGS"
into the Makefile. That seems to then get interpreted as
${C}MAKE_ASM_FLAGS. I'm not sure why things worked in Ninja, but I
suspect there is some underlying escaping bug in CMake somewhere.

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