Google Git
Sign in
boringssl / boringssl / f7b830d8df9f5578c748aa0283d44c59ea7eeb25
commitf7b830d8df9f5578c748aa0283d44c59ea7eeb25[log] [tgz]
authorAdam Langley <agl@google.com>Fri Sep 06 08:49:28 2019 -0700
committerCQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>Fri Sep 06 16:13:01 2019 +0000
tree753e335e5314795832085a66b072575730dd9c54
parent356a9a0895bbda5e78f5627dd546d4f09c380166 [diff]
Revert "Fix VS build when assembler is enabled"

This reverts commit 791f2822b25da0f69afc2aaa3d13c865af06fa82.

The use of $<COMPILE_LANGUAGE:CXX> causes issues for the Visual Studio
output of CMake[1] and the original CMake bug[2] was fixed in 3.13.0.

[1] https://github.com/grpc/grpc/pull/20100#issuecomment-528817457
[2] https://gitlab.kitware.com/cmake/cmake/merge_requests/2179

Change-Id: I74ec9d258d2c068e0c58d97deda8aa3794d387e5
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37364
Commit-Queue: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
1 file changed
tree: 753e335e5314795832085a66b072575730dd9c54
  1. .github/
  2. crypto/
  3. decrepit/
  4. fuzz/
  5. include/
  6. ssl/
  7. third_party/
  8. tool/
  9. util/
  10. .clang-format
  11. .gitignore
  12. API-CONVENTIONS.md
  13. BREAKING-CHANGES.md
  14. BUILDING.md
  15. CMakeLists.txt
  16. codereview.settings
  17. CONTRIBUTING.md
  18. FUZZING.md
  19. go.mod
  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.

Project links:

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