diff options
| author | David Benjamin <davidben@chromium.org> | 2015-10-18 06:39:22 +0300 |
|---|---|---|
| committer | Adam Langley <alangley@gmail.com> | 2015-10-26 21:36:23 +0300 |
| commit | 7a1eefd3cd8f697b33bf5348ea4d5c1e581dcdb6 (patch) | |
| tree | 85d66d8b0bfabf3ae8807fabdb12e1abe44ba746 /PORTING.md | |
| parent | 5d8b128095c08f9469a298ba54c8d875f6a2c58a (diff) | |
Deprecate SSL_library_init.
It just calls CRYPTO_library_init and doesn't do anything else. If
anything, I'd like to make CRYPTO_library_init completely go away too.
We have CRYPTO_once now, so I think it's safe to assume that, if ssl/
ever grows initialization needs beyond that of crypto/, we can hide it
behind a CRYPTO_once and not burden callers.
Change-Id: I63dc362e0e9e98deec5516f4620d1672151a91b6
Reviewed-on: https://boringssl-review.googlesource.com/6311
Reviewed-by: Adam Langley <alangley@gmail.com>
Diffstat (limited to 'PORTING.md')
| -rw-r--r-- | PORTING.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -149,10 +149,10 @@ OpenSSL has a number of different initialization functions for setting up error strings and loading algorithms, etc. All of these functions still exist in BoringSSL for convenience, but they do nothing and are not necessary. -The one exception is `CRYPTO_library_init` (and `SSL_library_init` which merely -calls it). In `BORINGSSL_NO_STATIC_INITIALIZER` builds, it must be called to -query CPU capabitilies before the rest of the library. In the default -configuration, this is done with a static initializer and is also unnecessary. +The one exception is `CRYPTO_library_init`. In `BORINGSSL_NO_STATIC_INITIALIZER` +builds, it must be called to query CPU capabitilies before the rest of the +library. In the default configuration, this is done with a static initializer +and is also unnecessary. ### Threading |