2018-11-03 17:26:35 +00:00
|
|
|
SUBDIRS=ossl_shim
|
2016-11-04 14:26:57 +00:00
|
|
|
{-
|
|
|
|
use File::Spec::Functions;
|
|
|
|
sub rebase_files
|
|
|
|
{
|
|
|
|
my ($base, $files) = @_;
|
|
|
|
return join(" ", map { "$base/$_" } split(/\s+/, $files));
|
|
|
|
}
|
2019-03-03 09:27:10 +00:00
|
|
|
our $apps_aux_src =
|
|
|
|
join(' ', map { "../apps/$_" } split(/\s+/, $target{apps_aux_src}));
|
2017-01-12 12:07:39 +00:00
|
|
|
""
|
2016-11-04 14:26:57 +00:00
|
|
|
-}
|
2016-04-14 12:44:15 +00:00
|
|
|
IF[{- !$disabled{tests} -}]
|
2019-01-30 17:18:34 +00:00
|
|
|
LIBS{noinst,has_main}=libtestutil.a
|
2017-04-28 12:46:18 +00:00
|
|
|
SOURCE[libtestutil.a]=testutil/basic_output.c testutil/output_helpers.c \
|
2017-06-05 17:32:05 +00:00
|
|
|
testutil/driver.c testutil/tests.c testutil/cb.c testutil/stanza.c \
|
2017-06-21 23:35:08 +00:00
|
|
|
testutil/format_output.c testutil/tap_bio.c \
|
2018-08-16 02:36:01 +00:00
|
|
|
testutil/test_cleanup.c testutil/main.c testutil/init.c \
|
2019-03-03 09:27:10 +00:00
|
|
|
testutil/options.c testutil/test_options.c \
|
|
|
|
testutil/apps_mem.c ../apps/opt.c {- $apps_aux_src; -}
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[libtestutil.a]=../include ../apps/include ..
|
2017-04-18 14:27:27 +00:00
|
|
|
DEPEND[libtestutil.a]=../libcrypto
|
|
|
|
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=\
|
2018-03-26 09:00:05 +00:00
|
|
|
versions \
|
2017-03-22 04:27:55 +00:00
|
|
|
aborttest test_test \
|
2018-09-16 22:09:25 +00:00
|
|
|
sanitytest rsa_complex exdatatest bntest \
|
2017-06-16 20:55:19 +00:00
|
|
|
ectest ecstresstest ecdsatest gmdifftest pbelutest ideatest \
|
2017-02-28 15:11:48 +00:00
|
|
|
md2test \
|
2017-02-28 14:18:27 +00:00
|
|
|
hmactest \
|
2017-02-28 15:58:46 +00:00
|
|
|
rc2test rc4test rc5test \
|
2017-05-11 23:31:18 +00:00
|
|
|
destest mdc2test \
|
2017-08-03 13:23:28 +00:00
|
|
|
dhtest enginetest casttest \
|
2018-07-17 20:04:09 +00:00
|
|
|
bftest ssltest_old dsatest dsa_no_digest_size_test exptest rsa_test \
|
2016-06-08 15:37:06 +00:00
|
|
|
evp_test evp_extra_test igetest v3nametest v3ext \
|
2019-01-24 02:15:54 +00:00
|
|
|
crltest danetest bad_dtls_test lhash_test sparse_array_test \
|
2019-02-22 02:21:33 +00:00
|
|
|
conf_include_test params_api_test \
|
2016-04-14 12:44:15 +00:00
|
|
|
constant_time_test verify_extra_test clienthellotest \
|
2017-03-14 02:37:26 +00:00
|
|
|
packettest asynctest secmemtest srptest memleaktest stack_test \
|
2016-04-14 12:44:15 +00:00
|
|
|
dtlsv1listentest ct_test threadstest afalgtest d2i_test \
|
2016-05-26 12:47:47 +00:00
|
|
|
ssl_test_ctx_test ssl_test x509aux cipherlist_test asynciotest \
|
2019-01-21 07:47:02 +00:00
|
|
|
bio_callback_test bio_memleak_test \
|
2016-11-19 21:52:34 +00:00
|
|
|
bioprinttest sslapitest dtlstest sslcorrupttest bio_enc_test \
|
2018-06-21 21:16:18 +00:00
|
|
|
pkey_meth_test pkey_meth_kdf_test evp_kdf_test uitest \
|
|
|
|
cipherbytes_test \
|
2018-09-08 08:09:32 +00:00
|
|
|
asn1_encode_test asn1_decode_test asn1_string_table_test \
|
2017-06-27 16:04:37 +00:00
|
|
|
x509_time_test x509_dup_cert_test x509_check_cert_pkey_test \
|
2017-01-13 16:00:26 +00:00
|
|
|
recordlentest drbgtest sslbuffertest \
|
2018-03-10 18:06:43 +00:00
|
|
|
recordlentest drbgtest drbg_cavs_test sslbuffertest \
|
2017-06-28 07:46:13 +00:00
|
|
|
time_offset_test pemtest ssl_cert_table_internal_test ciphername_test \
|
2018-03-19 14:01:39 +00:00
|
|
|
servername_test ocspapitest rsa_mp_test fatalerrtest tls13ccstest \
|
2019-02-06 16:42:50 +00:00
|
|
|
sysdefaulttest errtest gosttest \
|
2019-03-04 16:22:45 +00:00
|
|
|
context_internal_test aesgcmtest params_test
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2018-03-26 09:00:05 +00:00
|
|
|
SOURCE[versions]=versions.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[versions]=../include ../apps/include
|
2018-03-26 09:00:05 +00:00
|
|
|
DEPEND[versions]=../libcrypto
|
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[aborttest]=aborttest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[aborttest]=../include ../apps/include
|
2016-04-14 12:44:15 +00:00
|
|
|
DEPEND[aborttest]=../libcrypto
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[sanitytest]=sanitytest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sanitytest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[sanitytest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2018-09-16 22:09:25 +00:00
|
|
|
SOURCE[rsa_complex]=rsa_complex.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rsa_complex]=../include ../apps/include
|
2018-09-16 22:09:25 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[test_test]=test_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[test_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[test_test]=../libcrypto libtestutil.a
|
2017-03-22 04:27:55 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[exdatatest]=exdatatest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[exdatatest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[exdatatest]=../libcrypto libtestutil.a
|
2017-02-28 15:53:28 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[bntest]=bntest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bntest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[bntest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
|
|
|
SOURCE[ectest]=ectest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ectest]=../include ../apps/include
|
2017-04-28 04:06:11 +00:00
|
|
|
DEPEND[ectest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-06-16 20:55:19 +00:00
|
|
|
SOURCE[ecstresstest]=ecstresstest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ecstresstest]=../include ../apps/include
|
2017-06-16 20:55:19 +00:00
|
|
|
DEPEND[ecstresstest]=../libcrypto libtestutil.a
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[ecdsatest]=ecdsatest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ecdsatest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[ecdsatest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[gmdifftest]=gmdifftest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[gmdifftest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[gmdifftest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[pbelutest]=pbelutest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[pbelutest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[pbelutest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[ideatest]=ideatest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ideatest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[ideatest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[md2test]=md2test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[md2test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[md2test]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[hmactest]=hmactest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[hmactest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[hmactest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[rc2test]=rc2test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rc2test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[rc2test]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[rc4test]=rc4test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rc4test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[rc4test]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[rc5test]=rc5test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rc5test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[rc5test]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[destest]=destest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[destest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[destest]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[mdc2test]=mdc2test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[mdc2test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[mdc2test]=../libcrypto libtestutil.a
|
2016-04-14 12:44:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[dhtest]=dhtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[dhtest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[dhtest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[enginetest]=enginetest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[enginetest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[enginetest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[casttest]=casttest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[casttest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[casttest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[bftest]=bftest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bftest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[bftest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[ssltest_old]=ssltest_old.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ssltest_old]=.. ../include ../apps/include
|
2016-04-14 12:44:15 +00:00
|
|
|
DEPEND[ssltest_old]=../libcrypto ../libssl
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[dsatest]=dsatest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[dsatest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[dsatest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2018-07-17 20:04:09 +00:00
|
|
|
SOURCE[dsa_no_digest_size_test]=dsa_no_digest_size_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[dsa_no_digest_size_test]=../include ../apps/include
|
2018-07-17 20:04:09 +00:00
|
|
|
DEPEND[dsa_no_digest_size_test]=../libcrypto libtestutil.a
|
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[exptest]=exptest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[exptest]=../include ../apps/include
|
2017-04-26 13:11:50 +00:00
|
|
|
DEPEND[exptest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[rsa_test]=rsa_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rsa_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[rsa_test]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-08-01 18:19:43 +00:00
|
|
|
SOURCE[rsa_mp_test]=rsa_mp_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rsa_mp_test]=../include ../apps/include
|
2017-08-01 18:19:43 +00:00
|
|
|
DEPEND[rsa_mp_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-11-29 13:56:15 +00:00
|
|
|
SOURCE[fatalerrtest]=fatalerrtest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[fatalerrtest]=../include ../apps/include
|
2017-11-29 13:56:15 +00:00
|
|
|
DEPEND[fatalerrtest]=../libcrypto ../libssl libtestutil.a
|
2017-11-30 10:13:13 +00:00
|
|
|
|
|
|
|
SOURCE[tls13ccstest]=tls13ccstest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[tls13ccstest]=../include ../apps/include
|
2017-11-30 10:13:13 +00:00
|
|
|
DEPEND[tls13ccstest]=../libcrypto ../libssl libtestutil.a
|
2017-11-29 13:56:15 +00:00
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[evp_test]=evp_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[evp_test]=../include ../apps/include
|
2017-04-26 19:33:43 +00:00
|
|
|
DEPEND[evp_test]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[evp_extra_test]=evp_extra_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[evp_extra_test]=../include ../apps/include ../crypto/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[evp_extra_test]=../libcrypto libtestutil.a
|
2019-03-21 11:57:35 +00:00
|
|
|
IF[{- $disabled{fips} || !$target{dso_scheme} -}]
|
|
|
|
DEFINE[evp_extra_test]=NO_FIPS_MODULE
|
|
|
|
ENDIF
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[igetest]=igetest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[igetest]=../include ../apps/include
|
2017-04-20 04:23:10 +00:00
|
|
|
DEPEND[igetest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[v3nametest]=v3nametest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[v3nametest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[v3nametest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[crltest]=crltest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[crltest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[crltest]=../libcrypto libtestutil.a
|
2016-11-28 20:33:40 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[v3ext]=v3ext.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[v3ext]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[v3ext]=../libcrypto libtestutil.a
|
2016-06-08 15:37:06 +00:00
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[danetest]=danetest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[danetest]=../include ../apps/include
|
2017-05-02 12:32:26 +00:00
|
|
|
DEPEND[danetest]=../libcrypto ../libssl libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[constant_time_test]=constant_time_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[constant_time_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[constant_time_test]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[verify_extra_test]=verify_extra_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[verify_extra_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[verify_extra_test]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[clienthellotest]=clienthellotest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[clienthellotest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[clienthellotest]=../libcrypto ../libssl libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[bad_dtls_test]=bad_dtls_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bad_dtls_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[bad_dtls_test]=../libcrypto ../libssl libtestutil.a
|
2016-07-25 13:31:43 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[packettest]=packettest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[packettest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[packettest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[asynctest]=asynctest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asynctest]=../include ../apps/include
|
2016-04-14 12:44:15 +00:00
|
|
|
DEPEND[asynctest]=../libcrypto
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[secmemtest]=secmemtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[secmemtest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[secmemtest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[srptest]=srptest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[srptest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[srptest]=../libcrypto libtestutil.a
|
2016-01-29 22:33:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[memleaktest]=memleaktest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[memleaktest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[memleaktest]=../libcrypto libtestutil.a
|
2016-02-06 04:45:32 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[stack_test]=stack_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[stack_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[stack_test]=../libcrypto libtestutil.a
|
2017-03-14 02:37:26 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[lhash_test]=lhash_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[lhash_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[lhash_test]=../libcrypto libtestutil.a
|
2017-03-16 05:00:23 +00:00
|
|
|
|
2016-04-14 12:44:15 +00:00
|
|
|
SOURCE[dtlsv1listentest]=dtlsv1listentest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[dtlsv1listentest]=../include ../apps/include
|
2017-04-26 16:20:44 +00:00
|
|
|
DEPEND[dtlsv1listentest]=../libssl libtestutil.a
|
2016-02-25 21:48:36 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[ct_test]=ct_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ct_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[ct_test]=../libcrypto libtestutil.a
|
2015-10-25 16:43:55 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[threadstest]=threadstest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[threadstest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[threadstest]=../libcrypto libtestutil.a
|
2016-02-27 19:34:47 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[afalgtest]=afalgtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[afalgtest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[afalgtest]=../libcrypto libtestutil.a
|
2016-03-03 05:56:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[d2i_test]=d2i_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[d2i_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[d2i_test]=../libcrypto libtestutil.a
|
2016-03-30 20:37:05 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[ssl_test_ctx_test]=ssl_test_ctx_test.c ssl_test_ctx.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ssl_test_ctx_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[ssl_test_ctx_test]=../libcrypto ../libssl libtestutil.a
|
2016-03-17 14:14:30 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[ssl_test]=ssl_test.c ssl_test_ctx.c handshake_helper.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ssl_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[ssl_test]=../libcrypto ../libssl libtestutil.a
|
2016-03-17 14:14:30 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[cipherlist_test]=cipherlist_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[cipherlist_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[cipherlist_test]=../libcrypto ../libssl libtestutil.a
|
2016-04-06 14:03:06 +00:00
|
|
|
|
2016-06-29 20:59:50 +00:00
|
|
|
INCLUDE[ssl_test_ctx.o]=../include
|
Add TLSv1.3 post-handshake authentication (PHA)
Add SSL_verify_client_post_handshake() for servers to initiate PHA
Add SSL_force_post_handshake_auth() for clients that don't have certificates
initially configured, but use a certificate callback.
Update SSL_CTX_set_verify()/SSL_set_verify() mode:
* Add SSL_VERIFY_POST_HANDSHAKE to postpone client authentication until after
the initial handshake.
* Update SSL_VERIFY_CLIENT_ONCE now only sends out one CertRequest regardless
of when the certificate authentication takes place; either initial handshake,
re-negotiation, or post-handshake authentication.
Add 'RequestPostHandshake' and 'RequirePostHandshake' SSL_CONF options that
add the SSL_VERIFY_POST_HANDSHAKE to the 'Request' and 'Require' options
Add support to s_client:
* Enabled automatically when cert is configured
* Can be forced enabled via -force_pha
Add support to s_server:
* Use 'c' to invoke PHA in s_server
* Remove some dead code
Update documentation
Update unit tests:
* Illegal use of PHA extension
* TLSv1.3 certificate tests
DTLS and TLS behave ever-so-slightly differently. So, when DTLS1.3 is
implemented, it's PHA support state machine may need to be different.
Add a TODO and a #error
Update handshake context to deal with PHA.
The handshake context for TLSv1.3 post-handshake auth is up through the
ClientFinish message, plus the CertificateRequest message. Subsequent
Certificate, CertificateVerify, and Finish messages are based on this
handshake context (not the Certificate message per se, but it's included
after the hash). KeyUpdate, NewSessionTicket, and prior Certificate
Request messages are not included in post-handshake authentication.
After the ClientFinished message is processed, save off the digest state
for future post-handshake authentication. When post-handshake auth occurs,
copy over the saved handshake context into the "main" handshake digest.
This effectively discards the any KeyUpdate or NewSessionTicket messages
and any prior post-handshake authentication.
This, of course, assumes that the ID-22 did not mean to include any
previous post-handshake authentication into the new handshake transcript.
This is implied by section 4.4.1 that lists messages only up to the
first ClientFinished.
Reviewed-by: Ben Kaduk <kaduk@mit.edu>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/4964)
2017-12-18 21:52:28 +00:00
|
|
|
INCLUDE[handshake_helper.o]=.. ../include
|
2017-03-27 20:49:29 +00:00
|
|
|
INCLUDE[ssltestlib.o]=.. ../include
|
2016-05-02 18:46:51 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[x509aux]=x509aux.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[x509aux]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[x509aux]=../libcrypto libtestutil.a
|
2016-05-12 15:04:10 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[asynciotest]=asynciotest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asynciotest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[asynciotest]=../libcrypto ../libssl libtestutil.a
|
2016-05-26 12:47:47 +00:00
|
|
|
|
2018-03-19 13:20:53 +00:00
|
|
|
SOURCE[bio_callback_test]=bio_callback_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bio_callback_test]=../include ../apps/include
|
2018-03-19 13:20:53 +00:00
|
|
|
DEPEND[bio_callback_test]=../libcrypto libtestutil.a
|
|
|
|
|
2019-01-21 07:47:02 +00:00
|
|
|
SOURCE[bio_memleak_test]=bio_memleak_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bio_memleak_test]=../include ../apps/include
|
2019-01-21 07:47:02 +00:00
|
|
|
DEPEND[bio_memleak_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[bioprinttest]=bioprinttest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bioprinttest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[bioprinttest]=../libcrypto libtestutil.a
|
2016-08-04 22:32:36 +00:00
|
|
|
|
2019-02-22 02:21:33 +00:00
|
|
|
SOURCE[params_api_test]=params_api_test.c
|
|
|
|
INCLUDE[params_api_test]=../include ../apps/include
|
|
|
|
DEPEND[params_api_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[sslapitest]=sslapitest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sslapitest]=../include ../apps/include ..
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[sslapitest]=../libcrypto ../libssl libtestutil.a
|
2017-10-19 19:44:10 +00:00
|
|
|
|
|
|
|
SOURCE[ocspapitest]=ocspapitest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ocspapitest]=../include ../apps/include
|
2017-10-19 19:44:10 +00:00
|
|
|
DEPEND[ocspapitest]=../libcrypto libtestutil.a
|
2016-07-04 13:59:06 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[dtlstest]=dtlstest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[dtlstest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[dtlstest]=../libcrypto ../libssl libtestutil.a
|
2016-08-21 21:31:21 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[sslcorrupttest]=sslcorrupttest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sslcorrupttest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[sslcorrupttest]=../libcrypto ../libssl libtestutil.a
|
2016-10-31 20:50:26 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[bio_enc_test]=bio_enc_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[bio_enc_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[bio_enc_test]=../libcrypto libtestutil.a
|
2016-09-08 09:01:24 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[pkey_meth_test]=pkey_meth_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[pkey_meth_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[pkey_meth_test]=../libcrypto libtestutil.a
|
2016-11-19 21:52:34 +00:00
|
|
|
|
2017-08-03 19:44:18 +00:00
|
|
|
SOURCE[pkey_meth_kdf_test]=pkey_meth_kdf_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[pkey_meth_kdf_test]=../include ../apps/include
|
2017-08-03 19:44:18 +00:00
|
|
|
DEPEND[pkey_meth_kdf_test]=../libcrypto libtestutil.a
|
|
|
|
|
2018-06-21 21:16:18 +00:00
|
|
|
SOURCE[evp_kdf_test]=evp_kdf_test.c
|
2019-02-13 17:59:13 +00:00
|
|
|
INCLUDE[evp_kdf_test]=../include ../apps/include
|
2018-06-21 21:16:18 +00:00
|
|
|
DEPEND[evp_kdf_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[x509_time_test]=x509_time_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[x509_time_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[x509_time_test]=../libcrypto libtestutil.a
|
2017-02-17 18:00:15 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[recordlentest]=recordlentest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[recordlentest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[recordlentest]=../libcrypto ../libssl libtestutil.a
|
2017-03-06 16:56:42 +00:00
|
|
|
|
2017-06-27 16:04:37 +00:00
|
|
|
SOURCE[drbgtest]=drbgtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[drbgtest]=../include ../apps/include
|
2018-10-22 16:05:14 +00:00
|
|
|
DEPEND[drbgtest]=../libcrypto.a libtestutil.a
|
2017-06-27 16:04:37 +00:00
|
|
|
|
2018-07-24 01:16:38 +00:00
|
|
|
SOURCE[drbg_cavs_test]=drbg_cavs_test.c drbg_cavs_data_ctr.c \
|
|
|
|
drbg_cavs_data_hash.c drbg_cavs_data_hmac.c
|
2019-01-31 17:55:30 +00:00
|
|
|
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[drbg_cavs_test]=../include ../apps/include . ..
|
2018-03-10 18:06:43 +00:00
|
|
|
DEPEND[drbg_cavs_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[x509_dup_cert_test]=x509_dup_cert_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[x509_dup_cert_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[x509_dup_cert_test]=../libcrypto libtestutil.a
|
2017-04-20 19:33:42 +00:00
|
|
|
|
2017-06-04 19:16:40 +00:00
|
|
|
SOURCE[x509_check_cert_pkey_test]=x509_check_cert_pkey_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[x509_check_cert_pkey_test]=../include ../apps/include
|
2017-06-04 19:16:40 +00:00
|
|
|
DEPEND[x509_check_cert_pkey_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-04-12 21:24:43 +00:00
|
|
|
SOURCE[pemtest]=pemtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[pemtest]=../include ../apps/include
|
2017-04-12 21:24:43 +00:00
|
|
|
DEPEND[pemtest]=../libcrypto libtestutil.a
|
|
|
|
|
2017-07-08 18:28:15 +00:00
|
|
|
SOURCE[ssl_cert_table_internal_test]=ssl_cert_table_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ssl_cert_table_internal_test]=.. ../include ../apps/include
|
2017-07-08 18:28:15 +00:00
|
|
|
DEPEND[ssl_cert_table_internal_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-06-29 19:06:19 +00:00
|
|
|
SOURCE[ciphername_test]=ciphername_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ciphername_test]=../include ../apps/include
|
2017-06-29 19:06:19 +00:00
|
|
|
DEPEND[ciphername_test]=../libcrypto ../libssl libtestutil.a
|
|
|
|
|
2018-09-07 14:17:34 +00:00
|
|
|
SOURCE[servername_test]=servername_test.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[servername_test]=../include ../apps/include
|
2017-06-28 07:46:13 +00:00
|
|
|
DEPEND[servername_test]=../libcrypto ../libssl libtestutil.a
|
|
|
|
|
2018-05-09 11:05:39 +00:00
|
|
|
IF[{- !$disabled{cms} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=cmsapitest
|
2018-05-09 11:05:39 +00:00
|
|
|
SOURCE[cmsapitest]=cmsapitest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[cmsapitest]=../include ../apps/include
|
2018-05-09 11:05:39 +00:00
|
|
|
DEPEND[cmsapitest]=../libcrypto libtestutil.a
|
|
|
|
ENDIF
|
2018-05-01 08:32:30 +00:00
|
|
|
|
2016-10-12 15:13:31 +00:00
|
|
|
IF[{- !$disabled{psk} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=dtls_mtu_test
|
2016-10-12 15:13:31 +00:00
|
|
|
SOURCE[dtls_mtu_test]=dtls_mtu_test.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[dtls_mtu_test]=.. ../include ../apps/include
|
2017-04-26 16:20:44 +00:00
|
|
|
DEPEND[dtls_mtu_test]=../libcrypto ../libssl libtestutil.a
|
2016-10-12 15:13:31 +00:00
|
|
|
ENDIF
|
|
|
|
|
2016-11-03 10:31:12 +00:00
|
|
|
IF[{- !$disabled{shared} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=shlibloadtest
|
2016-10-18 13:16:35 +00:00
|
|
|
SOURCE[shlibloadtest]=shlibloadtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[shlibloadtest]=../include ../apps/include ../crypto/include
|
2016-10-18 13:16:35 +00:00
|
|
|
ENDIF
|
|
|
|
|
2016-09-08 09:01:24 +00:00
|
|
|
IF[{- $disabled{shared} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=cipher_overhead_test
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[cipher_overhead_test]=cipher_overhead_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[cipher_overhead_test]=.. ../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[cipher_overhead_test]=../libcrypto ../libssl libtestutil.a
|
2016-09-08 09:01:24 +00:00
|
|
|
ENDIF
|
2016-10-25 22:25:44 +00:00
|
|
|
|
2018-08-16 02:36:01 +00:00
|
|
|
SOURCE[uitest]=uitest.c ../apps/apps_ui.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[uitest]=.. ../include ../apps/include
|
2018-08-16 02:36:01 +00:00
|
|
|
DEPEND[uitest]=../libcrypto ../libssl libtestutil.a
|
2017-01-10 23:13:59 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[cipherbytes_test]=cipherbytes_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[cipherbytes_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[cipherbytes_test]=../libcrypto ../libssl libtestutil.a
|
2017-01-30 18:59:59 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[asn1_encode_test]=asn1_encode_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asn1_encode_test]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[asn1_encode_test]=../libcrypto libtestutil.a
|
2017-03-31 19:28:20 +00:00
|
|
|
|
2018-09-08 08:09:32 +00:00
|
|
|
SOURCE[asn1_decode_test]=asn1_decode_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asn1_decode_test]=../include ../apps/include
|
2018-09-08 08:09:32 +00:00
|
|
|
DEPEND[asn1_decode_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-07-26 17:18:50 +00:00
|
|
|
SOURCE[asn1_string_table_test]=asn1_string_table_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asn1_string_table_test]=../include ../apps/include
|
2017-07-26 17:18:50 +00:00
|
|
|
DEPEND[asn1_string_table_test]=../libcrypto libtestutil.a
|
|
|
|
|
2017-02-16 21:08:02 +00:00
|
|
|
SOURCE[time_offset_test]=time_offset_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[time_offset_test]=../include ../apps/include
|
2017-02-16 21:08:02 +00:00
|
|
|
DEPEND[time_offset_test]=../libcrypto libtestutil.a
|
|
|
|
|
2018-02-27 12:55:35 +00:00
|
|
|
SOURCE[conf_include_test]=conf_include_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[conf_include_test]=../include ../apps/include
|
2018-02-27 12:55:35 +00:00
|
|
|
DEPEND[conf_include_test]=../libcrypto libtestutil.a
|
|
|
|
|
2016-10-27 06:44:36 +00:00
|
|
|
# Internal test programs. These are essentially a collection of internal
|
2016-11-09 19:09:03 +00:00
|
|
|
# test routines. Some of them 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
|
2017-03-28 21:57:28 +00:00
|
|
|
# programs are forcibly linked with the static libraries, where all symbols
|
2018-10-25 13:55:15 +00:00
|
|
|
# are always available.
|
|
|
|
IF[1]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=asn1_internal_test modes_internal_test x509_internal_test \
|
Fix issues in ia32 RDRAND asm leading to reduced entropy
This patch fixes two issues in the ia32 RDRAND assembly code that result in a
(possibly significant) loss of entropy.
The first, less significant, issue is that, by returning success as 0 from
OPENSSL_ia32_rdrand() and OPENSSL_ia32_rdseed(), a subtle bias was introduced.
Specifically, because the assembly routine copied the remaining number of
retries over the result when RDRAND/RDSEED returned 'successful but zero', a
bias towards values 1-8 (primarily 8) was introduced.
The second, more worrying issue was that, due to a mixup in registers, when a
buffer that was not size 0 or 1 mod 8 was passed to OPENSSL_ia32_rdrand_bytes
or OPENSSL_ia32_rdseed_bytes, the last (n mod 8) bytes were all the same value.
This issue impacts only the 64-bit variant of the assembly.
This change fixes both issues by first eliminating the only use of
OPENSSL_ia32_rdrand, replacing it with OPENSSL_ia32_rdrand_bytes, and fixes the
register mixup in OPENSSL_ia32_rdrand_bytes. It also adds a sanity test for
OPENSSL_ia32_rdrand_bytes and OPENSSL_ia32_rdseed_bytes to help catch problems
of this nature in the future.
Reviewed-by: Andy Polyakov <appro@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5342)
2018-03-07 21:01:06 +00:00
|
|
|
tls13encryptiontest wpackettest ctype_internal_test \
|
2018-07-04 23:28:51 +00:00
|
|
|
rdrand_sanitytest property_test \
|
|
|
|
rsa_sp800_56b_test bn_internal_test
|
|
|
|
|
2016-11-09 19:09:03 +00:00
|
|
|
IF[{- !$disabled{poly1305} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=poly1305_internal_test
|
2016-11-09 19:09:03 +00:00
|
|
|
ENDIF
|
2017-03-04 22:11:16 +00:00
|
|
|
IF[{- !$disabled{chacha} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=chacha_internal_test
|
2017-03-04 22:11:16 +00:00
|
|
|
ENDIF
|
2017-01-11 21:38:44 +00:00
|
|
|
IF[{- !$disabled{siphash} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=siphash_internal_test
|
2017-01-11 21:38:44 +00:00
|
|
|
ENDIF
|
2018-04-06 13:45:41 +00:00
|
|
|
IF[{- !$disabled{sm2} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=sm2_internal_test
|
2018-04-06 13:45:41 +00:00
|
|
|
ENDIF
|
2017-10-31 05:19:14 +00:00
|
|
|
IF[{- !$disabled{sm4} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=sm4_internal_test
|
2017-10-31 05:19:14 +00:00
|
|
|
ENDIF
|
2018-02-20 14:53:40 +00:00
|
|
|
IF[{- !$disabled{ec} -}]
|
2019-02-12 14:00:20 +00:00
|
|
|
PROGRAMS{noinst}=ec_internal_test curve448_internal_test
|
2018-02-20 14:53:40 +00:00
|
|
|
ENDIF
|
2016-11-09 19:09:03 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[poly1305_internal_test]=poly1305_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[poly1305_internal_test]=.. ../include ../apps/include ../crypto/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[poly1305_internal_test]=../libcrypto.a libtestutil.a
|
2016-11-09 19:09:03 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[chacha_internal_test]=chacha_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[chacha_internal_test]=.. ../include ../apps/include ../crypto/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[chacha_internal_test]=../libcrypto.a libtestutil.a
|
2017-03-04 22:11:16 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[asn1_internal_test]=asn1_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asn1_internal_test]=.. ../include ../apps/include ../crypto/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[asn1_internal_test]=../libcrypto.a libtestutil.a
|
2016-11-09 19:09:03 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[modes_internal_test]=modes_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[modes_internal_test]=.. ../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[modes_internal_test]=../libcrypto.a libtestutil.a
|
2016-11-09 19:09:03 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[x509_internal_test]=x509_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[x509_internal_test]=.. ../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[x509_internal_test]=../libcrypto.a libtestutil.a
|
2016-11-17 22:58:46 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[tls13encryptiontest]=tls13encryptiontest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[tls13encryptiontest]=.. ../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[tls13encryptiontest]=../libcrypto ../libssl.a libtestutil.a
|
2017-01-23 14:53:44 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[wpackettest]=wpackettest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[wpackettest]=../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[wpackettest]=../libcrypto ../libssl.a libtestutil.a
|
2017-01-11 21:38:44 +00:00
|
|
|
|
2018-11-16 01:44:30 +00:00
|
|
|
SOURCE[property_test]=property_test.c
|
2019-05-01 10:02:43 +00:00
|
|
|
INCLUDE[property_test]=.. ../include ../apps/include
|
2018-11-16 01:44:30 +00:00
|
|
|
DEPEND[property_test]=../libcrypto.a libtestutil.a
|
|
|
|
|
2017-08-20 21:19:17 +00:00
|
|
|
SOURCE[ctype_internal_test]=ctype_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[ctype_internal_test]=.. ../crypto/include ../include ../apps/include
|
2017-08-20 21:19:17 +00:00
|
|
|
DEPEND[ctype_internal_test]=../libcrypto.a libtestutil.a
|
|
|
|
|
2019-01-24 02:15:54 +00:00
|
|
|
SOURCE[sparse_array_test]=sparse_array_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sparse_array_test]=../crypto/include ../include ../apps/include
|
2019-01-24 02:15:54 +00:00
|
|
|
DEPEND[sparse_array_test]=../libcrypto.a libtestutil.a
|
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[siphash_internal_test]=siphash_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[siphash_internal_test]=.. ../include ../apps/include ../crypto/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[siphash_internal_test]=../libcrypto.a libtestutil.a
|
2017-10-31 05:19:14 +00:00
|
|
|
|
2018-05-31 12:49:47 +00:00
|
|
|
SOURCE[sm2_internal_test]=sm2_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sm2_internal_test]=../include ../apps/include ../crypto/include
|
2018-05-31 12:49:47 +00:00
|
|
|
DEPEND[sm2_internal_test]=../libcrypto.a libtestutil.a
|
2018-04-06 13:45:41 +00:00
|
|
|
|
2017-10-31 05:19:14 +00:00
|
|
|
SOURCE[sm4_internal_test]=sm4_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sm4_internal_test]=.. ../include ../apps/include ../crypto/include
|
2017-10-31 05:19:14 +00:00
|
|
|
DEPEND[sm4_internal_test]=../libcrypto.a libtestutil.a
|
2019-02-12 14:00:20 +00:00
|
|
|
|
|
|
|
SOURCE[ec_internal_test]=ec_internal_test.c
|
|
|
|
INCLUDE[ec_internal_test]=../include ../crypto/ec ../apps/include ../crypto/include
|
|
|
|
DEPEND[ec_internal_test]=../libcrypto.a libtestutil.a
|
2017-12-12 19:55:38 +00:00
|
|
|
|
|
|
|
SOURCE[curve448_internal_test]=curve448_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[curve448_internal_test]=.. ../include ../apps/include ../crypto/ec/curve448
|
2017-12-12 19:55:38 +00:00
|
|
|
DEPEND[curve448_internal_test]=../libcrypto.a libtestutil.a
|
Fix issues in ia32 RDRAND asm leading to reduced entropy
This patch fixes two issues in the ia32 RDRAND assembly code that result in a
(possibly significant) loss of entropy.
The first, less significant, issue is that, by returning success as 0 from
OPENSSL_ia32_rdrand() and OPENSSL_ia32_rdseed(), a subtle bias was introduced.
Specifically, because the assembly routine copied the remaining number of
retries over the result when RDRAND/RDSEED returned 'successful but zero', a
bias towards values 1-8 (primarily 8) was introduced.
The second, more worrying issue was that, due to a mixup in registers, when a
buffer that was not size 0 or 1 mod 8 was passed to OPENSSL_ia32_rdrand_bytes
or OPENSSL_ia32_rdseed_bytes, the last (n mod 8) bytes were all the same value.
This issue impacts only the 64-bit variant of the assembly.
This change fixes both issues by first eliminating the only use of
OPENSSL_ia32_rdrand, replacing it with OPENSSL_ia32_rdrand_bytes, and fixes the
register mixup in OPENSSL_ia32_rdrand_bytes. It also adds a sanity test for
OPENSSL_ia32_rdrand_bytes and OPENSSL_ia32_rdseed_bytes to help catch problems
of this nature in the future.
Reviewed-by: Andy Polyakov <appro@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5342)
2018-03-07 21:01:06 +00:00
|
|
|
|
|
|
|
SOURCE[rdrand_sanitytest]=rdrand_sanitytest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[rdrand_sanitytest]=../include ../apps/include
|
Fix issues in ia32 RDRAND asm leading to reduced entropy
This patch fixes two issues in the ia32 RDRAND assembly code that result in a
(possibly significant) loss of entropy.
The first, less significant, issue is that, by returning success as 0 from
OPENSSL_ia32_rdrand() and OPENSSL_ia32_rdseed(), a subtle bias was introduced.
Specifically, because the assembly routine copied the remaining number of
retries over the result when RDRAND/RDSEED returned 'successful but zero', a
bias towards values 1-8 (primarily 8) was introduced.
The second, more worrying issue was that, due to a mixup in registers, when a
buffer that was not size 0 or 1 mod 8 was passed to OPENSSL_ia32_rdrand_bytes
or OPENSSL_ia32_rdseed_bytes, the last (n mod 8) bytes were all the same value.
This issue impacts only the 64-bit variant of the assembly.
This change fixes both issues by first eliminating the only use of
OPENSSL_ia32_rdrand, replacing it with OPENSSL_ia32_rdrand_bytes, and fixes the
register mixup in OPENSSL_ia32_rdrand_bytes. It also adds a sanity test for
OPENSSL_ia32_rdrand_bytes and OPENSSL_ia32_rdseed_bytes to help catch problems
of this nature in the future.
Reviewed-by: Andy Polyakov <appro@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5342)
2018-03-07 21:01:06 +00:00
|
|
|
DEPEND[rdrand_sanitytest]=../libcrypto.a libtestutil.a
|
2018-07-04 23:28:51 +00:00
|
|
|
|
|
|
|
SOURCE[rsa_sp800_56b_test]=rsa_sp800_56b_test.c
|
|
|
|
INCLUDE[rsa_sp800_56b_test]=.. ../include ../crypto/include ../crypto/rsa ../apps/include
|
|
|
|
DEPEND[rsa_sp800_56b_test]=../libcrypto.a libtestutil.a
|
|
|
|
|
|
|
|
SOURCE[bn_internal_test]=bn_internal_test.c
|
|
|
|
INCLUDE[bn_internal_test]=.. ../include ../crypto/include ../crypto/bn ../apps/include
|
|
|
|
DEPEND[bn_internal_test]=../libcrypto.a libtestutil.a
|
2016-10-25 22:25:44 +00:00
|
|
|
ENDIF
|
2016-10-26 21:12:48 +00:00
|
|
|
|
2016-11-09 19:09:03 +00:00
|
|
|
IF[{- !$disabled{mdc2} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=mdc2_internal_test
|
2016-10-27 19:42:45 +00:00
|
|
|
ENDIF
|
2016-10-27 20:18:50 +00:00
|
|
|
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[mdc2_internal_test]=mdc2_internal_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[mdc2_internal_test]=.. ../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[mdc2_internal_test]=../libcrypto libtestutil.a
|
2016-11-07 10:18:41 +00:00
|
|
|
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=asn1_time_test
|
2017-08-04 01:24:03 +00:00
|
|
|
SOURCE[asn1_time_test]=asn1_time_test.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[asn1_time_test]=../include ../apps/include
|
2017-08-04 01:24:03 +00:00
|
|
|
DEPEND[asn1_time_test]=../libcrypto libtestutil.a
|
|
|
|
|
2016-11-07 10:18:41 +00:00
|
|
|
# We disable this test completely in a shared build because it deliberately
|
|
|
|
# redefines some internal libssl symbols. This doesn't work in a non-shared
|
|
|
|
# build
|
|
|
|
IF[{- !$disabled{shared} -}]
|
2018-11-07 10:02:06 +00:00
|
|
|
PROGRAMS{noinst}=tls13secretstest
|
2017-04-18 14:47:11 +00:00
|
|
|
SOURCE[tls13secretstest]=tls13secretstest.c
|
2016-11-07 10:18:41 +00:00
|
|
|
SOURCE[tls13secretstest]= ../ssl/tls13_enc.c ../ssl/packet.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[tls13secretstest]=.. ../include ../apps/include
|
2017-04-18 14:47:11 +00:00
|
|
|
DEPEND[tls13secretstest]=../libcrypto ../libssl libtestutil.a
|
2016-11-07 10:18:41 +00:00
|
|
|
ENDIF
|
2017-01-13 16:00:26 +00:00
|
|
|
|
|
|
|
SOURCE[sslbuffertest]=sslbuffertest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sslbuffertest]=../include ../apps/include
|
2017-01-13 16:00:26 +00:00
|
|
|
DEPEND[sslbuffertest]=../libcrypto ../libssl libtestutil.a
|
2018-03-19 14:01:39 +00:00
|
|
|
|
|
|
|
SOURCE[sysdefaulttest]=sysdefaulttest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[sysdefaulttest]=../include ../apps/include
|
2018-03-19 14:01:39 +00:00
|
|
|
DEPEND[sysdefaulttest]=../libcrypto ../libssl libtestutil.a
|
2018-05-20 21:24:30 +00:00
|
|
|
|
|
|
|
SOURCE[errtest]=errtest.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[errtest]=../include ../apps/include
|
2018-05-20 21:24:30 +00:00
|
|
|
DEPEND[errtest]=../libcrypto libtestutil.a
|
2018-07-13 15:11:46 +00:00
|
|
|
|
|
|
|
SOURCE[gosttest]=gosttest.c ssltestlib.c
|
Move libapps headers into their own directory
This got triggered by test/testutil.h including ../apps/opt.h.
Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.
As a specific example, test/testutil/basic_output.c included
../testutil.h. Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.
The solution could have been to simply add apps/ as an inclusion
directory. However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.
Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
2019-02-12 10:37:43 +00:00
|
|
|
INCLUDE[gosttest]=../include ../apps/include ..
|
2018-07-13 15:11:46 +00:00
|
|
|
DEPEND[gosttest]=../libcrypto ../libssl libtestutil.a
|
2019-02-06 16:42:50 +00:00
|
|
|
|
2019-02-20 22:27:25 +00:00
|
|
|
SOURCE[aesgcmtest]=aesgcmtest.c
|
|
|
|
INCLUDE[aesgcmtest]=../include ../apps/include ..
|
|
|
|
DEPEND[aesgcmtest]=../libcrypto libtestutil.a
|
|
|
|
|
2019-02-06 16:42:50 +00:00
|
|
|
PROGRAMS{noinst}=context_internal_test
|
|
|
|
SOURCE[context_internal_test]=context_internal_test.c
|
|
|
|
INCLUDE[context_internal_test]=.. ../include ../apps/include
|
|
|
|
DEPEND[context_internal_test]=../libcrypto.a libtestutil.a
|
2019-02-20 21:55:43 +00:00
|
|
|
|
|
|
|
PROGRAMS{noinst}=provider_internal_test
|
|
|
|
DEFINE[provider_internal_test]=PROVIDER_INIT_FUNCTION_NAME=p_test_init
|
|
|
|
SOURCE[provider_internal_test]=provider_internal_test.c p_test.c
|
|
|
|
INCLUDE[provider_internal_test]=../include ../apps/include
|
|
|
|
DEPEND[provider_internal_test]=../libcrypto.a libtestutil.a
|
|
|
|
PROGRAMS{noinst}=provider_test
|
|
|
|
DEFINE[provider_test]=PROVIDER_INIT_FUNCTION_NAME=p_test_init
|
|
|
|
SOURCE[provider_test]=provider_test.c p_test.c
|
|
|
|
INCLUDE[provider_test]=../include ../apps/include
|
|
|
|
DEPEND[provider_test]=../libcrypto.a libtestutil.a
|
2019-03-31 13:17:58 +00:00
|
|
|
IF[{- !$disabled{module} -}]
|
2019-02-20 21:55:43 +00:00
|
|
|
MODULES{noinst}=p_test
|
|
|
|
SOURCE[p_test]=p_test.c
|
|
|
|
INCLUDE[p_test]=../include
|
|
|
|
IF[{- defined $target{shared_defflag} -}]
|
|
|
|
SOURCE[p_test]=p_test.ld
|
|
|
|
GENERATE[p_test.ld]=../util/providers.num
|
|
|
|
ENDIF
|
2019-03-31 13:26:26 +00:00
|
|
|
ENDIF
|
|
|
|
IF[{- $disabled{module} || !$target{dso_scheme} -}]
|
2019-04-04 10:35:47 +00:00
|
|
|
DEFINE[provider_test]=NO_PROVIDER_MODULE
|
|
|
|
DEFINE[provider_internal_test]=NO_PROVIDER_MODULE
|
2019-02-20 21:55:43 +00:00
|
|
|
ENDIF
|
2019-03-30 21:10:39 +00:00
|
|
|
DEPEND[]=provider_internal_test.conf
|
|
|
|
GENERATE[provider_internal_test.conf]=provider_internal_test.conf.in
|
2019-03-04 16:22:45 +00:00
|
|
|
|
|
|
|
PROGRAMS{noinst}=params_test
|
|
|
|
SOURCE[params_test]=params_test.c
|
|
|
|
INCLUDE[params_test]=.. ../include ../apps/include
|
|
|
|
DEPEND[params_test]=../libcrypto.a libtestutil.a
|
2016-08-04 22:32:36 +00:00
|
|
|
ENDIF
|
|
|
|
|
|
|
|
{-
|
2016-06-29 20:59:50 +00:00
|
|
|
use File::Spec::Functions;
|
2016-06-03 13:02:10 +00:00
|
|
|
use File::Basename;
|
2017-08-01 20:43:56 +00:00
|
|
|
use OpenSSL::Glob;
|
2016-06-03 13:02:10 +00:00
|
|
|
|
|
|
|
my @nogo_headers = ( "asn1_mac.h",
|
2018-05-01 21:25:16 +00:00
|
|
|
"opensslconf.h",
|
2016-06-03 13:02:10 +00:00
|
|
|
"__decc_include_prologue.h",
|
|
|
|
"__decc_include_epilogue.h" );
|
2018-03-19 17:54:27 +00:00
|
|
|
my @nogo_headers_re = ( qr/.*err\.h/ );
|
2016-06-03 13:02:10 +00:00
|
|
|
my @headerfiles = glob catfile($sourcedir,
|
|
|
|
updir(), "include", "openssl", "*.h");
|
|
|
|
|
|
|
|
foreach my $headerfile (@headerfiles) {
|
|
|
|
my $name = basename($headerfile, ".h");
|
|
|
|
next if $disabled{$name};
|
|
|
|
next if grep { $_ eq lc("$name.h") } @nogo_headers;
|
2018-03-19 17:54:27 +00:00
|
|
|
next if grep { lc("$name.h") =~ m/$_/i } @nogo_headers_re;
|
2016-06-03 13:02:10 +00:00
|
|
|
$OUT .= <<"_____";
|
|
|
|
|
2019-02-25 10:43:00 +00:00
|
|
|
PROGRAMS{noinst}=buildtest_c_$name
|
|
|
|
SOURCE[buildtest_c_$name]=buildtest_$name.c
|
2016-06-03 13:02:10 +00:00
|
|
|
GENERATE[buildtest_$name.c]=generate_buildtest.pl $name
|
2019-02-25 10:43:00 +00:00
|
|
|
INCLUDE[buildtest_c_$name]=../include
|
|
|
|
DEPEND[buildtest_c_$name]=../libssl ../libcrypto
|
|
|
|
_____
|
2019-02-28 12:28:43 +00:00
|
|
|
$OUT .= <<"_____" if $config{CXX} && !$disabled{"buildtest-c++"};
|
2019-02-25 10:43:00 +00:00
|
|
|
|
|
|
|
PROGRAMS{noinst}=buildtest_cc_$name
|
|
|
|
SOURCE[buildtest_cc_$name]=buildtest_$name.cc
|
|
|
|
GENERATE[buildtest_$name.cc]=generate_buildtest.pl $name
|
|
|
|
INCLUDE[buildtest_cc_$name]=../include
|
|
|
|
DEPEND[buildtest_cc_$name]=../libssl ../libcrypto
|
2016-06-03 13:02:10 +00:00
|
|
|
_____
|
|
|
|
}
|
2016-08-04 22:32:36 +00:00
|
|
|
-}
|