David Benjamin a70c75cfc0 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>		2014-09-12 00:10:53 +00:00
..
check.c	dh/check.c: check BN_CTX_get's return value.	2014-06-20 13:17:39 -07:00
CMakeLists.txt	Inital import.	2014-06-20 13:17:32 -07:00
dh_asn1.c	Inital import.	2014-06-20 13:17:32 -07:00
dh_error.c	Move public headers to include/openssl/	2014-07-14 22:42:18 +00:00
dh_impl.c	Windows build fixes.	2014-08-11 22:10:02 +00:00
dh_test.c	Add a CRYPTO_library_init and static-initializer-less build option.	2014-09-12 00:10:53 +00:00
dh.c	Windows build fixes.	2014-08-11 22:10:02 +00:00
internal.h	Inital import.	2014-06-20 13:17:32 -07:00
params.c	Inital import.	2014-06-20 13:17:32 -07:00