Unittest for cryspr methods

[jeandube]

Fixed returned values of fallback kmwrap and kmunwrap methods
Made cryspr.h header C++ compatible (for unittest prog)

[ethouris]

The build fails due to lacking include directories; this is the first test that would include (indirectly) the openssl headers. For the SRT library (haicrypt in particular) this is fixed by this line:

target_include_directories(haicrypt_virtual PRIVATE  ${SSL_INCLUDE_DIRS})

The same like this must be added to the test_srt application.

[jeandube]

test_cryspr was tested with OpenSSL and GnuTLS but I was not able to test with mbedTLS. Is it part of the Travis or Appveyor tests?

[maxsharabayko]

test_cryspr was tested with OpenSSL and GnuTLS but I was not able to test with mbedTLS. Is it part of the Travis or Appveyor tests?

Unfortunately, both Travis and AppVeyor build only OpenSSL. Support for all those build options is in the TODO list.

[ethouris]

Unit tests should be enabled only with C++11 simply because the test driver library requires it - it doesn't matter if it's required by the test procedure itself.

[jeandube]

With this change GCC 4.6.3 which is not C++11 can generate a working test_srt.
Here the cmake command I use cmake . -DUSE_ENCLIB=openssl -DENABLE_CXX11=OFF -DENABLE_UNITTESTS=1 -DHAVE_COMPILER_GNU_COMPAT=OFF -DINSTALL_GTEST=OFF

[ethouris]

But I guess if you set -DINSTALL_GTEST=OFF, you must have had the gtest library already installed and compiled by a C++11-compliant compiler.

And anyway, ENABLE_UNITTESTS enables all unit tests, and it suffices that at least one of them requires C++11, as most of them do, to require C++11-compliance for all of them. The idea for the unit tests is that they are run automatically, so even splitting them into those that require C++11 and those that don't doesn't make much sense, as all are intended to be run anyway.