openssl
/
openssl
mirror of https://github.com/openssl/openssl
1
0
Fork 0
Code Issues Releases Wiki Activity

Explain the deal with internal test programs 

Reviewed-by: Emilia Käsper <emilia@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/1789)
This commit is contained in:
Richard Levitte 2016-10-27 08:44:36 +02:00
parent ab6e147c49
commit b5b7c61fe3
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
test/build.info
View File

@ -299,6 +299,21 @@ IF[{- !$disabled{tests} -}]
DEPEND[cipher_overhead_test]=../libcrypto ../libssl
ENDIF
# Internal test programs. These are essentially a collection of internal
# test routines. Because they sometimes need to reach internal symbols that
# aren't available through the shared library (at least on Linux, Solaris,
# Windows and VMS, where the exported symbols are those listed in util/*.num),
# these programs may be built on files directly picked from inside crypto/
# or ssl/, to test using symbols that exist in those specific files. These
# programs will also be linked with libcrypto / libssl, so we don't pick
# out more specific files than necessary.
# This might mean we have multiply defined symbols, but since linking is
# ordered with object files first and libraries after, the symbols from the
# object files will be chosen before those in the libraries. This is handled
# properly by all linkers.
# Note that when building with static libraries, none of those extra files
# are needed, since all symbols are available anyway, regardless of what's
# listed in util/*.num.
IF[{- !$disabled{poly1305} -}]
PROGRAMS_NO_INST=poly1305_internal_test
ENDIF