Google Git
Sign in
pigweed / third_party / boringssl / boringssl / 68f84f5c40644e029ed066999448696b01caba7a
commit68f84f5c40644e029ed066999448696b01caba7a[log] [tgz]
authorTom Anderson <thomasanderson@chromium.org>Wed May 24 20:20:11 2017 -0700
committerCQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>Thu May 25 17:26:44 2017 +0000
tree8ea0dabb165e21a44e536abd538b5a987d76781c
parent806e18c022bd137326f5c19e2b0c7f466e93ed54 [diff]
Add missing dependencies on exe_and_shlib_deps

Corresponding Chrome CL:
https://codereview.chromium.org/2899403004/

BUG=chromium:723069

Change-Id: I0ab9c104263d12e8251adf60d89ad19cf0436785
Reviewed-on: https://boringssl-review.googlesource.com/16664
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
1 file changed
tree: 8ea0dabb165e21a44e536abd538b5a987d76781c
  1. .github/
  2. crypto/
  3. decrepit/
  4. fipstools/
  5. fuzz/
  6. include/
  7. infra/
  8. ssl/
  9. third_party/
  10. tool/
  11. util/
  12. .clang-format
  13. .gitignore
  14. API-CONVENTIONS.md
  15. BUILDING.md
  16. CMakeLists.txt
  17. codereview.settings
  18. CONTRIBUTING.md
  19. FUZZING.md
  20. INCORPORATING.md
  21. LICENSE
  22. PORTING.md
  23. README.md
  24. sources.cmake
  25. 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.

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