Google Git
Sign in
boringssl / boringssl / 625f68bf35248c9f47c964ce782567aafa4e2f55
commit625f68bf35248c9f47c964ce782567aafa4e2f55[log] [tgz]
authorDavid Benjamin <davidben@google.com>Fri Jan 26 13:37:48 2024 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jan 26 19:02:14 2024 +0000
tree2bf72ca4d37c3d1aaad37fe3391c9a42d7d10feb
parent8378dad8af30bc825518ef38098c4a50cfa99728 [diff]
Tweak generate_build_files.py output to pass gn's formatter

Chromium's presubmits check for files to be correctly formatted. While
this is automatically generated, the tooling doesn't know this. Just
output in the format it expects, which is that length 0 and length one
lists are formatted differently.

Change-Id: I3c5bec884db302f780c5c53429dfe26cb4731d58
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65828
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
1 file changed
tree: 2bf72ca4d37c3d1aaad37fe3391c9a42d7d10feb
  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: