|author||David Benjamin <firstname.lastname@example.org>||Tue Sep 03 19:27:17 2019 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Wed Sep 04 17:20:44 2019 +0000|
Fix cross-compile of Android on Windows. When running the ARM perlasm files on Windows, close STDOUT fails. There appears to be some weird quirk on Windows when one replaces STDOUT with a pipe. The x86_64.pl files all avoid this by opening OUT and then setting *STDOUT=*OUT. Align all the ARM files with that pattern. See https://ci.appveyor.com/project/conscrypt/conscrypt Change-Id: Ibee9427a05d806f7f23a6d9817394cfabf2f534a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37324 Reviewed-by: Kenny Root <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> Commit-Queue: Adam Langley <email@example.com>
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: