libolm - Implementation of the olm and megolm cryptographic ratchets

Age	Commit message (Collapse)	Author
2016-05-24	Build the crypto libs as C99	Richard van der Hoff
	Some of the crypto libs rely on UINT64_C, which in glibc 2.17 and earlier was not defined for C++ code (see https://sourceware.org/bugzilla/show_bug.cgi?id=15366).
2016-05-23	Rename olm.hh to olm.h	Richard van der Hoff

2016-05-23	Fix warnings and set -Werror	Richard van der Hoff

2016-05-23	Add support for building fuzzers using american fuzzy lop	Mark Haines
	Builds fuzzers using http://lcamtuf.coredump.cx/afl/
2016-05-23	Fix make clean to remove the library and all the .d files	Mark Haines

2016-05-23	Move comment to correct location	Mark Haines

2016-05-23	Don't use $^ cause that includes the header files	Mark Haines

2016-05-23	Use a rule to make the build directories	Mark Haines

2016-05-23	Put the .o files in separate directories so we can have both release and ↵	Mark Haines
	debug versions
2016-05-20	Fix the Makefile so that it works with a clean git checkout	Mark Haines

2016-05-20	Remove dep files for js objects on clean	Richard van der Hoff

2016-05-20	Add an 'all' target to the Makefile	Richard van der Hoff
	So that we can build everything together.
2016-05-20	Use a version script to restrict symbols in the .so	Richard van der Hoff
	We want to stop aes_* and sha_* functions leaking out of our .so, as well as internal _olm_* symbols. This also means we need to link the unit tests against the objects. Possibly we should distinguish between unit tests and integration tests.
2016-05-20	Add support for building the JS wrappers to the Makefile	Richard van der Hoff
	Now that we have C and C++, we need to split the compile and link steps (because we need different flags for the C and C++ files), so this is easier with a Makefile.
2016-05-20	Add a makefile	Richard van der Hoff
	Replace the python scripts for building the shared lib and tests with a Makefile, which makes it easier to handle a mix of C and C++.