summaryrefslogtreecommitdiff
path: root/crypto/build.info
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2018-12-11 23:58:29 +0100
committerRichard Levitte <levitte@openssl.org>2019-03-06 11:15:13 +0100
commit2390c573aa598b715eb592c9b4da50a71453347a (patch)
treecff4c281e12afe6665530b4825ff5b1adfdef40a /crypto/build.info
parent8ab53b193a8e95bb2998744bc184146eb1ddcc23 (diff)
downloadopenssl-new-2390c573aa598b715eb592c9b4da50a71453347a.tar.gz
Add generic trace API
The idea is that the application shall be able to register output channels or callbacks to print tracing output as it sees fit. OpenSSL internals, on the other hand, want to print thoses texts using normal printing routines, such as BIO_printf() or BIO_dump() through well defined BIOs. When the application registers callbacks, the tracing functionality sets up an internal BIO that simply forwards received text to the appropriate application provided callback. Co-authored-by: Dr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com> Reviewed-by: Paul Dale <paul.dale@oracle.com> (Merged from https://github.com/openssl/openssl/pull/8198)
Diffstat (limited to 'crypto/build.info')
-rw-r--r--crypto/build.info1
1 files changed, 1 insertions, 0 deletions
diff --git a/crypto/build.info b/crypto/build.info
index 94ed06e65f..e3e9ceeec1 100644
--- a/crypto/build.info
+++ b/crypto/build.info
@@ -13,6 +13,7 @@ SOURCE[../libcrypto]=\
ebcdic.c uid.c o_time.c o_str.c o_dir.c o_fopen.c ctype.c \
threads_pthread.c threads_win.c threads_none.c getenv.c \
o_init.c o_fips.c mem_sec.c init.c context.c sparse_array.c \
+ trace.c \
{- $target{cpuid_asm_src} -} {- $target{uplink_aux_src} -}
DEPEND[cversion.o]=buildinf.h