boringssl/ssl/pqueue/CMakeLists.txt

include_directories(../../include)

add_library(
	pqueue

	OBJECT

	pqueue.c
)

add_executable(
	pqueue_test

	pqueue_test.c
)

target_link_libraries(pqueue_test ssl crypto)
Inital import. Initial fork from f2d678e6e89b6508147086610e985d4e8416e867 (1.0.2 beta). (This change contains substantial changes from the original and effectively starts a new history.) 2014-06-20 20:00:00 +01:00			`include_directories(../../include)`

			`add_library(`
			`pqueue`

			`OBJECT`

			`pqueue.c`
			`)`
Add tests for pqueue Reorder the tests in all_tests.sh to be in alphabetical order. Change-Id: Idc6df6ab4a25709312a6f58635061bb643582c70 Reviewed-on: https://boringssl-review.googlesource.com/1680 Reviewed-by: Adam Langley <agl@google.com> 2014-08-30 03:41:39 +01:00
			`add_executable(`
			`pqueue_test`

			`pqueue_test.c`
			`)`

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:11:15 +01:00			`target_link_libraries(pqueue_test ssl crypto)`