| commit | 6b34d549451ca98d1ab758bf509e2a03b4eedc4a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Fri Feb 05 21:58:39 2016 -0500 |
| committer | Adam Langley <agl@google.com> | Mon Feb 08 18:12:36 2016 +0000 |
| tree | 70225097971f8fddd727ce4515acf7ffb1490d2d | |
| parent | 089cba090cae76d8c3c316bee5662cddc5395ca6 [diff] |
Prefer MSVC over GCC if both are in %PATH%. Notably, putting Strawberry Perl in %PATH% will usually end up putting a copy of gcc in %PATH%, which trips up people trying to build on Windows. This is arguably misusing the variable (normally set by the generator), but it should work. Change-Id: I13a011eb33688ae928a56cce266edd2759a3cb32 Reviewed-on: https://boringssl-review.googlesource.com/7070 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: