tree 97fa841a4edd2b3a4dc831f34c0d33a704e8206c
parent 1195796045e1f8bbd1ed311b2cbd8b9d87f2074a
author David Benjamin <davidben@chromium.org> 1410477075 -0400
committer Adam Langley <agl@google.com> 1410480653 +0000

Add a CRYPTO_library_init and static-initializer-less build option.

Chromium does not like static initializers, and the CPU logic uses one to
initialize CPU bits. However, the crypto library lacks an explicit
initialization function, which could complicate (no compile-time errors)
porting existing code which uses crypto/, but not ssl/.

Add an explicit CRYPTO_library_init function, but make it a no-op by default.
It only does anything (and is required) if building with
BORINGSSL_NO_STATIC_INITIALIZER.

Change-Id: I6933bdc3447fb382b1f87c788e5b8142d6f3fe39
Reviewed-on: https://boringssl-review.googlesource.com/1770
Reviewed-by: Adam Langley <agl@google.com>