Don't define OPENSSL_ENGINES in test recipes, do it in Makefiles instead
authorRichard Levitte <levitte@openssl.org>
Sat, 5 Mar 2016 12:11:37 +0000 (13:11 +0100)
committerRichard Levitte <levitte@openssl.org>
Thu, 17 Mar 2016 09:10:59 +0000 (10:10 +0100)
commita717738b45fa7ae90cf3dac0870b8d1ea2a8e173
tree930272dba40ea23bd8bbfaa612e693b674a291ca
parent909289dfc31ca7b02652e3e9ed4e2df754fd258f
Don't define OPENSSL_ENGINES in test recipes, do it in Makefiles instead

In most builds, we can assume that engines live in the build tree
subdirectory "engines".  This was hard coded into the tests that use
the engine ossltest.

However, that hard coding is tedious, it would need to be done in
every test recipe, and it's an incorrect assumption in some cases.

This change has us play it safe and let the build files tell the
testing framework where the engines are.

Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
13 files changed:
Configurations/descrip.mms.tmpl
Configurations/unix-Makefile.tmpl
test/Makefile.in
test/recipes/70-test_sslcertstatus.t
test/recipes/70-test_sslextension.t
test/recipes/70-test_sslsessiontick.t
test/recipes/70-test_sslskewith0p.t
test/recipes/70-test_sslvertol.t
test/recipes/70-test_tlsextms.t
test/recipes/90-test_networking.t
util/pl/BC-32.pl
util/pl/VC-32.pl
util/pl/unix.pl