Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Leave FIND_LIBRARIES empty if CRYPTO_LIBDIR is empty.
Propagate CRYPTO_LIBDIR to .sh scripts.
CRYPTO_LIBDIR must be an absolute path (for now)
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Guido Vranken <guidovranken@gmail.com>
|
|
The host is the OS that the binary will run on,
this ensures that CPU_RISC is set to true.
Run all test with make runtest.
|
|
incorporates #366 and adapts to it
|
|
Ensure this target is also run in travis-ci
|
|
Fixes builds with srcdir != objdir.
|
|
This is a private test file.
|
|
This will fix issues as reported in #229 where we fail to complete builds
because the libary suffix variable is not set.
|
|
This framework is header only which is the main reason it was chosen.
More information about it (not that much really!) can be found in [1].
The license is MIT and the copyright notice is included in the header
cutest.h so I think putting the file in our repo is OK wrt licensing.
Location of new files and structure for unit tests are up for discussion.
Note that I am including "srtp.c" in "test_srtp.c" in order to test it's
internal (static) functions.
Alternatively we could try to test from public API, however that is
already done in for example /test/srtp_driver.c which functions more
like an integration/module test.
The purpose of the unit tests are (for now) testing of lower level
functions that are not exposed
in the public API.
Alternative layout could be to put the unit tests in a /test/ folder in
the root directory of the file that is being tested.
Alternative frameworks considered:
cmocka [2] does not require external tools and have support for mocking.
It does however require more than a header to run. This seems like the
best bet if we do want to introduce a unit test system that supports more
advanced functionality.
CTest [3] introduces a dependency on cmake - depending on both make and
cmake seems kind of annoying.
Google Test [4] requires a C++98 compatible compiler, requiring this for
a C library seems excessive.
[1] https://github.com/mity/cutest
[2] https://cmocka.org/
[3] https://cmake.org/cmake/help/v3.0/manual/ctest.1.html
[4] https://github.com/google/googletest
|
|
Apply MKI Support Patch
|
|
|
|
|
|
|
|
|
|
If in the future it is enabled then remember to not include
private header
|
|
The shared library setup only checked for mingw, not cygwin.
Which resulted in a empty shared library variables such as suffix and
linker flags.
This fixes it by checking both for cygwin and mingw on the same line,
resulting in the same setup for both.
|
|
On Windows, adding -fPIC will print a warning for every compilation unit
about all code being positioned independent. I.e. the flag is redundant.
This removes the unconditional -fPIC flag from CPPFLAGS in Makefile.in and
sets it in configure.in instead, except when compiling for *cygwin*
or *mingw*.
|
|
The libsrtp2.pc file should always be generated and installed regardless
of whether pkg-config is installed on the build machine.
For instance, if a machine is dedicated to building packages, but doesn't
have pkg-config installed, that doesn't mean users of the finished package
doesn't want the pkg-config file.
The libsrtp2.pc file, generated from the libsrtp2.pc.in template, is only
dependent on the correct AC_SUBST() calls in configure.in. I.e. pkg-config
does not have to be installed to generate it.
This removes the entire HAVE_PKG_CONFIG concept and always generates and
installs the libsrtp2.pc file.
|
|
For configure.in, this additionally replaces
the few tabs there where with spaces.
|
|
|
|
|
|
Otherwise we create a symlink with the same name as the target, which will
create a symlink pointing to itself.
|
|
within an independent directory (e.g. mkdir build; ../configure; make)
|
|
|
|
|
|
Thanks for the contribution.
|
|
|
|
Regression was added in commit cae277e4377acc90ef787d09ed0d82968bbe809a
|
|
Regression was added in commit cae277e4377acc90ef787d09ed0d82968bbe809a
|
|
|
|
The pkg-config file is generated in the build directory, so we need to
copy it from there.
|
|
RNG in libsrtp wasn't using a particularly good random source anyway. Downstream applications should use OpenSSL or some other random source that's compliant with SP-800-90.
|
|
a clean.
|
|
|
|
and OS X
Also ensure that the shared library is versioned, and an implib is created on
Windows.
|
|
libsrtp 1.x. Header files are now installed into /usr/local/include/srtp2.
|
|
library. Libraries such as OpenSSL provide a newer SP800-90 compliant DRBG.
|
|
Removed unused hex utils from libsrtp.a and moved them to the app layer.
|
|
general purpose crypto library.
|
|
used as a general purpose crypto library. The RNG provided by libsrtp is old and not current with the latest standards, such as SP800-90.
|
|
practices for library development. Removed GDOI configure option because it's not used anywhere in the code.
|
|
|