Google Git
Sign in
boringssl / boringssl.git / a0cb725b3905c6d596d5adbd7fa2ec034f182b4f
commita0cb725b3905c6d596d5adbd7fa2ec034f182b4f[log] [tgz]
authorMatthew Braithwaite <mab@google.com>Wed Apr 26 14:34:52 2017 -0700
committerCQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>Thu Apr 27 17:02:14 2017 +0000
tree99dc1b60f743d826653ba7de7cfc9cc0b2aee6c8
parentfb383f0c3dbdc6dd9f8b23a4742bcab352aa9265 [diff]
generate_build_files: enforce uniqueness of test names.

This changes the test names to use the last component, which is
generally the test data file, in place of the 2nd component, which is
less unique.

Change-Id: I182ad1ffb59595a6579a6a87e07af6cb11036e93
Reviewed-on: https://boringssl-review.googlesource.com/15584
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: 99dc1b60f743d826653ba7de7cfc9cc0b2aee6c8
  1. .github/
  2. crypto/
  3. decrepit/
  4. fuzz/
  5. include/
  6. infra/
  7. ssl/
  8. third_party/
  9. tool/
  10. util/
  11. .clang-format
  12. .gitignore
  13. API-CONVENTIONS.md
  14. BUILDING.md
  15. CMakeLists.txt
  16. codereview.settings
  17. CONTRIBUTING.md
  18. FUZZING.md
  19. INCORPORATING.md
  20. LICENSE
  21. PORTING.md
  22. README.md
  23. 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: