Richard Levitte 45502bfe19 Always build library object files with shared library cflags ... This takes us away from the idea that we know exactly how our static libraries are going to get used. Instead, we make them available to build shareable things with, be it other shared libraries or DSOs. On the other hand, we also have greater control of when the shared library cflags. They will never be used with object files meant got binaries, such as apps/openssl or test/test*. With unified, we take this a bit further and prepare for having to deal with extra cflags specifically to be used with DSOs (dynamic engines), libraries and binaries (applications). Reviewed-by: Rich Salz <rsalz@openssl.org>		2016-02-20 16:51:31 +01:00
..
build.info	unified build scheme: add build.info files	2016-02-01 12:46:58 +01:00
ct.ec	Handle CT error macros separately	2015-10-21 23:57:29 +02:00
ct_err.c	Remove /* foo.c */ comments	2016-01-26 16:40:43 -05:00
ct_lib.c	Fix some missing or faulty header file inclusions	2015-12-30 14:54:29 +01:00
Makefile.in	Always build library object files with shared library cflags	2016-02-20 16:51:31 +01:00