commit | 48e2be247a02a727487b19e745fcf6c24cc8823d | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Dec 21 12:37:00 2016 -0500 |
committer | Adam Langley <agl@google.com> | Wed Dec 21 18:11:25 2016 +0000 |
tree | 5e031becfa31945ae87c65e7d366abf0ec914388 | |
parent | 28feb92a5b363576afeb42670a9976595dfb1795 [diff] |
Include the type in empty vector literals. Chromium on Linux builds against libstdc++'s debug mode which makes clang unhappy due to: ../crypto/bytestring/bytestring_test.cc:910:7: error: chosen constructor is explicit in copy-initialization {}, ^~ /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/debug/vector:79:7: note: constructor declared here vector(const _Allocator& __a = _Allocator()) ^ I believe this was fixed here, but it's too recent: https://github.com/gcc-mirror/gcc/commit/36f540c70ba27e441bd07111a2107b8993382905 Change-Id: I2942d153e1278785c3b81294bc99b86f297cf719 Reviewed-on: https://boringssl-review.googlesource.com/12967 Reviewed-by: Adam Langley <agl@google.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: